WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

TCP transport channel custom properties

If you are using a TCP transport channel, you can add the following custom property to the configuration settings for that channel.

To add a custom property:
  1. In the administrative console, click Servers > Application servers > server_name, and then select one of the following options, depending on the type of chain you are creating:
    • Under SIP Container Settings, click SIP container transport chains.
    • Under Web container settings, click Web container transport chains.
    • [z/OS] Under Container services, click ORB Service > ORB Service Transport Chains.
    • Under Server messaging, click either Messaging engine inbound transports or WebSphere MQ link inbound transports.
  2. Select the transport chain that includes the TCP channel for which you want to specify the custom property.
  3. Select the TCP inbound channel.
  4. Click Custom properties > New, and then, under General Properties, specify the name of the custom property in the Name field and a value for this property in the Value field. You can also specify a description of this property in the Description field.
  5. Click Apply or OK.
  6. Click Save to save your configuration changes.
  7. Restart the server.

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.

listenBacklog

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

zaioFreeInitialBuffers [z/OS]

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 Linkage Editor (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.

Note: If you set this property to true, you must also add the following argument to the JVM generic arguments that are configured for the application server that is using this TCP channel:
-Dcom.ibm.ws.buffermgmt.impl.WsByteBufferPoolManagerImpl=com.ibm.ws.buffermgmt.impl.ZOSWsByteBufferPoolManagerImpl
Data type String
Default false



Related tasks
Configuring transport chains
Related information
[z/OS] Fine tuning the LE heap
Reference topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/rrun_chain_tcpcustom.html