Forum Discussion
astokes_6920
Nimbostratus
NimbostratusHTTP monitor with HEAD, not GET
While using the following monitor, I'm finding that the web servers are keeping TCP sessions in the TIME_WAIT state, rather than closing them outright.
GET /serverin.html HTTP/1.1\r\nCo...
Justinian_48178Nimbostratus
NimbostratusWe're having this exact same issue. We did tune our TIME_WAIT timers (and as a good measure increased our max ports), but I'd still love to find a way around this if anyone has one.
For record, the Registry changes for Time_Wait and max ports are (obviously use these at your own risk... I place no warranty on registry suggestions)
To add and configure the MaxUserPort parameter:
1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Right-click on Parameters and select New DWORD Value. Type MaxUserPort in the Name data box, type 65534 (Decimal) in the Value data box, and then click OK.
NOTE: The default setting for the MaxUserPort value is 5000 (Decimal).
4. Quit Registry Editor.
To add and configure the TcpTimedWaitDelay parameter:
1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Right-click on Parameters and select New DWORD Value. Type TcpTimedWaitDelay in the Name data box, type 60 (Decimal) in the Value data box, and then click OK.
NOTE: The default setting for the TcpTimedWaitDelay value is 240 (Decimal), which equals four minutes. Never set this value below 30.
4. Quit Registry Editor.
