MQSeries.net :: View topic - TCP connection close from client side

vickas · Posted: Thu Apr 21, 2016 9:52 am Post subject:

Hie All,

I have a client flow which exchanges data & heartbeats over TCP/IP .
The requirement is to exchange the data maintaining a persistent connection to the TCP servers & to close the connection only when there isnt any heartbeats/Ack from the servers .

so I used 2 TCP client output nodes ( same IP & port ) .
1 TCP client output node ( close connection : NO ) to send the heartbeats & data msgs continuously & other TCP client output node to close the connection ( connected to close terminal ) if heartbeats are not recieved for a time period more than 60 secs .

besides this , i have a Tcp client input node to recieve the acks/msgs from the server .

All the Data & heartbeats are exchanged continously as expected but
The issue is , we see frequent disconnections at the server End . They say that the connection close initiation is happening from the esb server frequently but from the interface logs we see continous flow of data & heartbeats .

when we did netstat -an | grep 11111

it always shows the connection as ESTABLISHED as such
tcp 0 1 ::ffff:xx.xxx.xxx.xx:3333 (esb server ) ::ffff:xx.xx.xx.xx:1111(tcp server ) ESTABLISHED

but sometimes along with the following we see TIME_WAIT
tcp 0 0 xx.xxx.xxx.xx:6643 (esb server ) xx.xx.xx.xx:1111(tcp server ) TIME_WAIT
tcp 0 1 ::ffff:xx.xxx.xxx.xx:3333 (esb server ) ::ffff:xx.xx.xx.xx:1111(tcp server ) ESTABLISHED

tcp 0 0 xx.xxx.xxx.xx:8829 (esb server ) xx.xx.xx.xx:1111(tcp server ) TIME_WAIT
tcp 0 1 ::ffff:xx.xxx.xxx.xx:3333 (esb server ) ::ffff:xx.xx.xx.xx:1111(tcp server ) ESTABLISHED

what can be the issue ??
ran the trace , the flow isnt closing any connections explicitly .
have harcoded the ip address & port on the nodes ( didnt use any configurable service ) & using ONE CONNECTION option available .