| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Timeout value MQOPEN 2009 |
« View previous topic :: View next topic » |
| Author |
Message
|
| MABeatty1978 |
 Posted: Fri Nov 11, 2016 7:03 am Post subject: Timeout value MQOPEN 2009 |
 |
|
Acolyte
Joined: 17 Jul 2014
Posts: 54
|
Is there some kind of time out value for an MQOPEN or an MQCONN?
Just had an event where my application did and MQOPEN to a cluster q that after exactly 5 minutes, failed with an mqrc2009. I believe the con and open came from an mq client. It looks like the conn succeeded, but it tried for 5 minutes to do the open.
Thank you |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Nov 11, 2016 7:13 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
When you googled 'mqrc 2009' what did you discover?
_________________
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 |
|
|
| MABeatty1978 |
| Posted: Fri Nov 11, 2016 7:26 am Post subject: |
|
|
Acolyte
Joined: 17 Jul 2014
Posts: 54
|
The most common causes for 2009 are the following:
1. A firewall has terminated the connection.
2. An IOException caused the socket to be closed.
3. An explicit action caused the socket to be closed by one end.
4. The queue manager is offline.
5. The maximum number of channels allowed by the queue manager are already open.
6. A configuration problem in the Queue Connection Factory (QCF).
1. I don't believe there is a firewall
2. How would I know if this happend
3. I don't believe there is anything that would do this
4. Qmgr is online
5. How do I look at this
6. Not using JMS, using MQ C libraries. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Nov 11, 2016 7:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
2009 = connection failed.
MQ client ships each MQ call cross-network to the qmgr; and the qmgr components ship ReasonCode back to client for each call. Any temporary or permanent hiccup may result in a 2009.
Look at client error logs, network, system and MQ error logs. Often there will be a tcp error logged.
_________________
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.
Last edited by bruce2359 on Fri Nov 11, 2016 8:33 am; edited 1 time in total |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Nov 11, 2016 8:27 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Client Platform? Version of MQ?
Server Platform? Version of MQ?
Contents of mqclient.ini
Contents of qm.ini
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| 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
|
|
|
|
