| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQIPT Socket Closed errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| rconn2 |
 Posted: Wed Sep 08, 2021 2:19 pm Post subject: MQIPT Socket Closed errors |
 |
|
Voyager
Joined: 09 Aug 2007
Posts: 79
Location: MD, USA
|
Our new set-ups of MQIPT (version 9.2) are logging these errors:
conn close ERROR Socket Closed
conn close ERROR Connection Reset
Our queue managers log AMQ9209 and AMQ9999 errors.
These happen around 5 - 30 plus minutes for each connection.
These errors are immediately followed by new OK connections. So, these are connection hiccups.
This is our first use of MQIPT. When tested internally, the logs have been clean. These errors are occurring with routes we just configured with external queue managers (across firewall, F5 boundaries).
I'm guessing this is some network issue but wonder if there's a likely or typical cause. Also, if there's some setting I might make on the MQ channels or the routes that might mitigate these errors.
For now, the MQ channels work, but intermittently go into Retry and decrement the short retry count, and sometimes even begin the long retry count.
Any guidance would be greatly appreciated! I've used this forum in the past (I'm an MQ SME and this forum helped me become one). Thanks! |
|
| Back to top |
|
 |
| hughson |
| Posted: Thu Sep 09, 2021 2:28 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Are these connections idle at the time?
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| rconn2 |
| Posted: Thu Sep 09, 2021 1:19 pm Post subject: |
|
|
Voyager
Joined: 09 Aug 2007
Posts: 79
Location: MD, USA
|
Yes, idle. Last night I set one channel's hb's to 3000 (50 minutes). The log show socket closed errors exactly 5 minutes after each hb.
00:00 Sender --> hb
00:00 hb returned; Channel shows Running
00:05 socket closed; connection reset; Channel still shows Running
00:50 Sender --> hb
00:50 hb fails
00:50 Channel retries (and starts); counter decrements; Channel Running
00:55 socket closed; connection reset; Channel still shows Running
etc.
So, something is causing a socket close 5 minutes after every connection open.
This evening, I set hb's to 1 minute (to get under that 5 minute socket close interval) and so far so good (crossing fingers). I'll check again in the am.
Our network is very convoluted (I'm not a network SME), so I guess there's some time-out somewhere. But, if the 2 minute hb fixes things, then all is okay.
I'm thinking of using 2 minutes for hb's (if 1 minute continues to work, I'll try 2). Also I upped the short retry interval to 20 at 1 minute each, and decreased the long retries to 10 minutes.
I'll post back tomorrow what happens. |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Sep 09, 2021 1:32 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| rconn2 wrote: |
| Yes, idle. Last night I set one channel's hb's to 3000 (50 minutes). The log show socket closed errors exactly 5 minutes after each hb. |
Classic firewall behavior.
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| rconn2 |
| Posted: Fri Sep 10, 2021 7:30 pm Post subject: |
|
|
Voyager
Joined: 09 Aug 2007
Posts: 79
Location: MD, USA
|
Thanks Morag. I set the HBINT to 60 from 300 (which ran exactly into the 5 minute time-outs) and the errors have so far gone away.
I'll experiment and probably up the HBINT to 120 or so (comfortably under 5 minutes). And, a DISCINT of 3600 (1 hour) -- plenty long enough and easy to remember.
On the plus side, I filled in some gaps in my MQ knowledge: short and long timers and intervals and hb's. An interesting thing I found was "zombie" channels: the status showed Running, but the socket had closed soon after a successful hb or successful Retry. So, the channels thought they were Running, but went into another Retry upon the next hb or message.
Another thing is I discovered the 5 minute time-out issue by setting the HBINT to 50 minutes. By doing this, I could see what happened when a channel was completely idle -- and so, saw the time-outs. |
|
| 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
|
|
|
|
