If you are using a TCP transport channel, you can add the following custom property to the configuration settings for that channel.
Following are the descriptions of the TCP transport channel custom properties provided with the product. These properties are not shown on the settings page for an TCP transport channel.
Use the listenBacklog property to specify the maximum number of outstanding connect requests that the operating system can 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 is rejected. The value of this property is specific to each transport.
If you need to control the number of concurrent connections, use the Maximum open connections field on the administrative console TCP transport channel settings page.
Data type | Integer |
Default | 511 |
Use the zaioFreeInitialBuffers property to indicate that the TCP channel should release the initial read buffers used on new connections as soon as these buffers are no longer needed for the connection. By default, this initial read buffer is cached for each connection. When a connection is closed, the read buffer is reused to avoid a memory allocation. This process works well for non-persistent connections, where there is one request per connection. However, for highly persistent connections, the buffer might be held for a considerable amount of time even though it is not being used. For workloads that require a large number of connected clients, this situation can cause a shortage of Language Environment (LE) heap space. Unless your workload consists mainly of non-persistent connections, you should set this custom property to true to enable the release of the initial read buffers.
-Dcom.ibm.ws.buffermgmt.impl.WsByteBufferPoolManagerImpl=com.ibm.ws.buffermgmt.impl.ZOSWsByteBufferPoolManagerImpl
Data type | String |
Default | false |