WebSphere Web server plug-in connections
The WebSphere Web server plug-in is used to establish and maintain persistent connections to the Application Server HTTP and HTTPS transports.
When the plug-in is ready to send a request to the Application Server, it first checks its connection pool for existing connections. If an existing connection is available the plug-in checks its connection status. If the status is still good, the plug-in uses that connection to send the request. If a connection does not exist, the plug-in creates one. If a connection exists but has been closed by the Application Server, the plug-in closes that connection and opens a new one.
Once a connection is established between a plug-in and the Application Server, it will not be closed unless the Application Server closes it for one of the following reasons:
- The time limit specified on the ConnectionKeepAliveTimeout HTTP
transport custom property has expired.
- The maximum number of requests which can be processed on a single keep
alive has been exceeded. (This number is set using the ConnectionMaxKeepAliveRequests HTTP
transport custom property.)
- The maximum number of concurrent keep alive (persistent) connections across all HTTP transports has been exceeded. (This number is set using the MaxKeepAliveConnections HTTP transport custom property.)
- The Application Server is shutting down.
Even if the Application Server closes a connection, the plug-in will not know that it has been closed until it tries to use it again. The connection will be closed if one of the following events occur:
- The plug-in receives a new HTTP request and tries to reuse the existing
connection.
- The number of httpd processes drop because the Web server is not
receiving any new HTTP requests. (For the IHS Web server, the number of httpd processes
that are kept alive depends on the value specified on the Web server's MinSpareServers
directive.)
- The Web server is stopped and all httpd processes are terminated, and their corresponding sockets are closed.
Note: Sometimes, if a heavy request load is stopped or decreased abruptly on a particular Application Server, a lot of the plug-in's connections to that Application Server will be in CLOSE_WAIT state. Because these connections will be closed the first time the plug-in tries to reuse them, having a large number of connections in CLOSE-WAIT state should not affect performance
Configuring Web server plug-ins
HTTP transport custom properties