Use this page to set custom properties for an HTTP transport.
You can set these properties on either the Web Container or HTTP Transport Custom Properties pages. When set on the Web container Custom Properties page, all transports inherit the properties. Setting the same properties on a transport overrides like settings defined for a Web container.
To specify custom properties for a specific transport on the HTTP Transport:
Following is a list of custom properties provided with the Application Server. These properties are not shown on the settings page for an HTTP transport.
Data type | Integer | |
Default | For WebSphere Application Server running on a distributed operating system, the default is 5 seconds. | For WebSphere Application Server for z/OS, the default is 120 seconds. |
Data type | Integer | |
Default | For WebSphere Application Server on a distributed platform, the default is 5 seconds. | For WebSphere Application Server for z/OS, the default is 30 seconds. |
Use this property to set the maximum amount of time, in seconds, that the J2EE server will wait for an application component to respond to an HTTP request. Set this variable for each of the HTTP transport definitions on the server. You will need to set this variable for both SSL transport and non-SSL transport. If the response is not received within the specified length of time, the servant (region) might fail with ABEND EC3 and RSN=04130007. Setting this timer prevents client applications from waiting for a response from an application component that might be deadlocked, looping, or encountering other processing problems that cause the application component to hang.
Use the server custom properties protocol_http_timeout_output_recovery and protocol_https_timeout_output_recovery, described in this article, to indicate the recovery action that you want taken on timeouts for requests received over the HTTP and HTTPS transports.
Data type | Integer |
Default | 300 seconds |
Set this value to the number of concurrent connections that you would like to allow. Keep in mind that a single client browser might need to open multiple concurrent connections (perhaps 4 or 5); however, also keep in mind that increasing this value consumes more kernel resources. The value of this property is specific to each transport.
Data type | Integer |
Default | 511 |
Use the MaxKeepAliveConnections property to specify the maximum number of concurrent keep alive (persistent) connections across all HTTP transports. To make a particular transport close connections after a request, you can set MaxKeepAliveConnections to 0 (zero) or you can set KeepAliveEnabled to false on that transport.
The Web server plug-in keeps connections open to the application server as long as it can. However, if the value of this property is too small, performance is negatively impacted because the plug-in has to open a new connection for each request instead of sending multiple requests through one connection.
If socket states other than ESTABLISHED are in effect for many connections, application server connections might be impacted because of a lack of available TCP memory. If this situation does not occur, the Application Server should be able to continue handling connections until the operating system has reached its limits.
Data type | Integer |
Default | If you are not using a Web server plug-in, 90% of the maximum number
of threads in the Web container thread pool. This prevents all of the threads
from being held by keep alive connections so that there are threads available
to handle new incoming connect requests. If you are using a Web server plug-in, the plug-in maintains controls the connections between the plug-in and the application server. The connection in KeepAlive state that was established between the plug-in and the application server can be reused by any client. |
For WebSphere Application Server on Distributed Platforms, if this property is set to 0 (zero), the connection stays open as long as the application server is running.
Data type | Integer | |
Default | For WebSphere Application Server on Distributed Platforms the default value is 100 requests | For WebSphere Application Server for z/OS the default value is 50 requests |
Data type | string |
Default | true |
PERMIT CB.BIND.servername CLASS(CBIND) ID(clientCertUserid) ACCESS(CONTROL)
Data type | String |
Default | false |
Data type | String |
Default | false |
Note: This property must be set to false for Secure Sockets Layer (SSL) client certificate authentication to work.
Data type | String |
Default | false |
Note: This property must be set to false for Secure Sockets Layer (SSL) client certificate authentication to work.
Data type | String |
Default | true |
The setBufferSize() API method can be used to override the value specified for this custom property at the individual servlet level.
Data type | Integer |
Default | 32000 bytes |