| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB 8.0 - TCPIPServerInput node IDLE Connection issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| gabrielj |
 Posted: Thu Nov 19, 2015 1:35 am Post subject: WMB 8.0 - TCPIPServerInput node IDLE Connection issue |
 |
|
Novice
Joined: 16 Nov 2014
Posts: 23
Location: Muscut,Perth,Sydney,Bangalore,Hydrabad,Coimbatore
|
Hi All,
WMB version: 8.0.0.4
OS: HP-Ux
We have an issue in one of our flow which contains TCPIPServerInput / TCPIPServerOutput. Recently we observed that ulimit values are getting increase day by day. once the upper limit reached then flow getting hanged. We used LSOF command to check which process opening to many files and we found that so many connections are in IDLE state.
The flow look like below.
TCPIPServerInput -> Compute -> TCPIPServerOutput
TCPIPServerInput configuration.
Timeout waiting for the data: 60 sec
Close Connection : After Timeout
Input Stream modification: Leave unchanged.
Output Stream modification: Leave unchanged
TCPIPServerOutput Configuration
Timeout sending data Record: 10
Close Connection : After Timeout
Input Stream modification: Leave unchanged.
Output Stream modification: Leave unchanged
I have tested following scenario.
1. When Timeout happens, WMB close the connection and which is not shown in the lsof output.
2. if the client terminates the connection then the connection goes in idle state. Our OS has keepAlive time value as 30mins. These connections(IDLE) not cleaned by OS after keepalive time expired.
Some of the lsof output
lsof | grep TCP | grep 6062
DataFlowE 24329 mqsi 111u IPv4 0xe0000001a5f30080 0t0 TCP mwdev1:6062->192.168.149.44:54319 (IDLE)
DataFlowE 24329 mqsi 232u IPv4 0xe0000001cdd50400 0t0 TCP *:6062 (LISTEN)
DataFlowE 24329 mqsi 261u IPv4 0xe0000001ea6f9100 0t0 TCP mwdev1:6062->192.168.149.44:54202 (IDLE)
DataFlowE 24329 mqsi 262u IPv4 0xe0000001a7a63980 0t27 TCP mwdev1:6062->192.168.149.44:54204 (IDLE)
DataFlowE 24329 mqsi 266u IPv4 0xe0000001ea6f9400 0t0 TCP mwdev1:6062->192.168.149.44:54166 (IDLE)
TCPServerInput node running on 6062 port number
Here the question is.
1. How to get rid of these idle connection when client unexpectedly terminate?. Is there any setting we have to do in WMB node level or need to tweak any OS level parameters?
Thanks in advance. |
|
| Back to top |
|
 |
| timber |
| Posted: Fri Nov 20, 2015 2:23 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| How to get rid of these idle connection when client unexpectedly terminate? |
Before answering that, I need to know what research you have done. This is a known problem with TCP/IP connections ( not WMB/IIB ), and there is no point in me telling you things that you already know.
| Quote: |
| Is there any setting we have to do in WMB node level or need to tweak any OS level parameters? |
There is no 'setting' ( no single property that you can configure ). You can ask WMB/IIB to drop a specific TCP/IP connection - you have to send a message to the TCPIPClientOutput node with the ConnectionID specified in the LocalEnvironment. That might be one way of closing connections that are known to be 'orphaned' by a badly-behaved client. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
