Use this page to set custom properties for an HTTP transport.
On a distributed platform, if, when migrating from Version 5.x, you indicate that you want to continue using an HTTP transport to handle your HTTP requests, your Version 5 transports are migrated for you. If you are not migrating from WebSphere Application Server Version 5.x, you must set up an HTTP transport channel to handle your HTTP requests.
The use of IPv6 (Internet Protocol Version 6) and WS-AT (Web Services Atomic Transactions) are not supported on HTTP transports; they are only supported on HTTP transport channel chains.
If you are using HTTP transports, you can set the following custom properties on either the Web Container or HTTP Transport Custom Properties panel on the administrative console. 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.
Use the ConnectionIOTimeOut property to specify the maximum amount of time, in seconds, that the J2EE server waits for the complete HTTP request to arrive. 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. The J2EE server starts the timer after the connection has been established, and cancels the connection if a complete request does not arrive within the specified maximum time limit. Specifying a value of zero disables the time out function.
Data type | Integer |
Default | For the i5/OS and distributed platforms: 5 seconds |
Use the ConnectionKeepAliveTimeout property to specify the maximum number of seconds to wait for the next request on a keep alive connection.
Data type | Integer |
Default | For the i5/OS and distributed platforms: 5 seconds |
This property is only valid for distributed platforms. Use the MaxConnectBacklog property to specify the maximum number of outstanding connect requests that the operating system will buffer while it waits for the application server to accept the connections. If a client attempts to connect when this operating system buffer is full, the connect request will be rejected.
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 |
This property is only valid for distributed platforms. It is ignored on the z/OS platform because asynchronous I/O sockets are used to maintain connections in that environment.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. The application server might not accept a new connection under a heavy load if there are too many sockets in TIME_WAIT state. If all client requests are going through the Web server plug-in and there are many TIME_WAIT state sockets for port 9080, the application server is closing connections prematurely, which decreases performance. The application server closes the connection from the plug-in, or from any client, for any of the following reasons:
Data type | Integer |
Default | 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. |
Use the MaxKeepAliveRequests property to specify the maximum number of requests which can be processed on a single keep alive connection. This parameter can help prevent denial of service attacks when a client tries to hold on to a keep-alive connection. The Web server plug-in keeps connections open to the application server as long as it can, providing optimum performance.
On the distributed platforms, when this property is set to 0 (zero), the connection stays open as long as the application server is running.
Data type | Integer |
Default | 100 requests |
This property is only valid for i5/OS and distributed platforms. Use the KeepAliveEnabled property to specify whether or not to keep connections alive
Data type | String |
Default | true |
This property is only valid for i5/OS and distributed platforms. Use the Trusted property to indicate that the application server can use the private headers that the Web server plug-in adds to requests.
Data type | String |
Default | false |
Related tasks
Modifying the default Web container configuration
Tuning the application serving environment
Configuring HTTP transports
Related reference
HTTP transport settings
Administrative console page features
Web container custom properties