| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ7- AMQ9271- Channel timeout |
« View previous topic :: View next topic » |
| Author |
Message
|
| SAFraser |
 Posted: Tue Sep 21, 2010 3:27 pm Post subject: |
 |
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Thanks, Glenn! We looked at that link too. (Mr. Google doesn't have much to say about this one, does he?)
We have not gotten any FDCs associated with these timeouts. We also are very close to current on OS patches to our Solaris platform.
We've downloaded and are using supportpac mo06, which allows us to quickly see the timestamps of these AMQ9271 across all queue managers on a zone. It's been a terrific improvement over looking at individual queue manager logs.
Jeff, Many times, these errors appear rather randomly. But we found one zone where all ten queue managers suffered the AMQ9271 within three minutes of each other. That can't possibly be an issue internal to MQ; it's got to be something either at the server or the network layer, don't you think? The OS logs show no evidence of socket errors.
In a foolhardy maintenance event over Labor Day, we patched both the OS and MQ on all our development servers. Since that time, we've had only a handful of timeouts.
Also, Jeff, we specify KeepAlive as 'yes' for each queue manager, and we have reduced the OS-level keepalive. But we have not tweaked KAINT and HBINT. Thanks for that pointer, we'll look at it right away.
I appreciate everyone's continued interest in our issue.  |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Sep 21, 2010 5:23 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So, again. Presumably you are seeing these AMQ errors in a *specific* log file, either on the Server or on the Client install side.
Are there errors on the *other* side, that match the time stamp (relative to the clock offset of the two systems)? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Sep 21, 2010 8:13 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| That can't possibly be an issue internal to MQ |
That's been my experience. MQ is merely reporting the TCP protocol symptoms that it sees.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Wed Sep 22, 2010 6:50 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| There are no errors whatsoever on the *other* side. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Sep 22, 2010 7:28 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
I've seen this one-sided issue as well. It seems to point to a network issue on your side, in one o/s domain (LPAR?), perhaps a bad nic-card, a router/switch/cable dropping packets and/or the connection.
One of my clients ended up swapping out a 3' long patch cable to resolve a similar problem.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 01, 2012 6:13 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
| What are recommended values for KAINT and HBINT to help with this problem (which we have as well)? |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
