eG Help

The SWSKeepAliveTest provides server's HTTP level keep alive statistics for the process of the instance. The name keep alive should not be confused with TCP keep-alives. Also, note that the name keep-alive was changed to PersistentConnections in HTTP 1.1, but Web Server continues to refer to these connections as keep-alive connections. Most modern browsers request a web page from the server through persistent connections with the web server. The connection is kept alive even after processing a request, so that it will be easier to process a similar request.

Measurement	Description	Measurement Unit	Interpretation
Keep_Alive_Hits	Indicates the number of times a request was successfully received from a connection that was kept alive during last measurement period.	Number
No_of_Connections_Added	Indicates the current number of connections in keep-alive mode.	Number
Maximum_Connection_Size	Indicates the maximum number of connections allowed in keep-alive mode simultaneously.	Number
No_of_Conns_Flushed	Indicates the number of times the server close a connection as when the total number of connections that are added exceedes the keep-alive maximum connections setting during last measurement period.	Number	The server does not close existing connections when the keep-alive count exceeds the maximum connection size. Instead, new keep-alive connections are refused and the number of connections refused count is incremented.
No_of_Conns_Refused	Indicates the number of times the server could not complete the connection to a keep-alive thread during last measurement period.	Number	Possibly due to too many persistent connections (or when total number of connections added exceeds the keep-alive maximum connections setting).
Keep_Alive_Timeouts	Indicates the number of times the server closes idle keep-alive connections as the client connections will be timed out without any activity during last measurement period.	Number
Connection_Timeout	Indicates the time before idle keep-alive connections are closed.	Secs