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.
    • 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
[Updated in July 2011]

soReuseAddr

Use the soReuseAddr custom property to control bind behavior. When the WebSphere Application Server is restarted, if the inbound TCP channels have problems trying to bind the listening socket, errors are printed into the SystemOut file until either the bind is successful or the number of allowed bind attempts has been passed. This custom property helps to avoid repeated error messages during the bind process.

For inbound TCP channel binding environments, you can avoid the repeated error messages by using the SoReuseAddr custom property to affect TCP inbound channel processing. When SoReuseAddr is set to 1 , the TCP channel is forced to try each bind attempt with the re-use option set to true on the socket. The restart of the WebSphere Application Server processes first binding attempt, despite those sockets in TIME_WAIT state.
Note: The first restart after applying the soReuseAddr property processes the previous instance of binding (which was bound with false). Two restarts might be required before re-use success is achieved with re-use set to true all the time. Also, you can wait until all the TIME_WAIT sockets have disappeared before restarting.
Data type Integer
Default 0
[Updated in July 2011]
jul2011



Related tasks
Configuring transport chains
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 4:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-dist&topic=rrun_chain_tcpcustom
File name: rrun_chain_tcpcustom.html