MQSeries.net :: View topic - TCP/IP Ports

AJStar · Posted: Sat Sep 05, 2009 1:39 am Post subject:

Hi All,

I have a problem with TCP/IP connection timeouts while using the TCPIPClient Configurable service.

I'm using WMB 6.1.0.3. My message flow consists of a TCPIPClientOutput node and a TCPIPClientReceive node amongst others.

Example:
MQInput -> Compute1 -> TCPIPClientOutput -> TCPIPClientReceive -> Compute2 -> MQOutput

These are the properties set in -
TCPIPClientOutput node:
Timeout sending data records (seconds) - 20
Close connection - No

TCPIPClientReceive node:
Timeout waiting for data record (seconds) - 10
Close connection - After Data has been Received

In both the nodes, the Connection details property is set with a configurable service name, say TCPCONN. The properties are
TCPIPClient
TCPCONN
ExpireConnectionSec='60'
Hostname='localhost'
MaxReceiveRecordBytes='100000000'
MaximumConnections='100'
MinimumConnections='0'
Port='9020'
SO_KEEPALIVE='false'
SO_LINGER='false'
SO_LINGER_TIMEOUT_SEC='-1'
SO_RCVBUF='0'
SO_SNDBUF='0'
TCP_NODELAY='false'
TrafficClass='-1'

Case1: When a request is sent to the port 9020 by the TCPIPClientOutput node and a successful response is received by the TCPIPClientReceive node, the connection is closed as expected.

Case2: If there is a timeout receiving a response at the TCPIPClientReceive node, then the connection remains open as expected. And when another request comes in, it re-uses the open connection and closes it if the response is received successfully.

Case3: This is the problem case. If there is a timeout receiving a response at the TCPIPClientReceive node, then the connection remains open as expected. And when there is no request for the next 60 sec (ExpireConnectionSec in configurable service TCPCONN), then I expected the connection to be closed. But it did not.

I also performed another test to confirm if the ExpireConnectionSec attribute actually works. I tested the flow without the TCPIPClientReceive node (MQInput -> Compute1 -> TCPIPClientOutput).
Here once a connection is opened and the request is sent by the TCPIPClientOutput node, the connection is closed after the idle period of 60 sec. But within the 60 sec if I post another message, the open connection is re-used and the idle period of 60 secs does not close the connection.

Anybody know what the issue is? Or is there a gap in my understanding about how this works? Please share your views/experience.
_________________
Regards
AJ