| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQJMS2008: failed to open MQ queue exception |
« View previous topic :: View next topic » |
| Author |
Message
|
| msvpraveen |
 Posted: Mon Apr 06, 2009 1:05 am Post subject: MQJMS2008: failed to open MQ queue exception |
 |
|
Novice
Joined: 07 Jul 2005
Posts: 12
|
I have an application in which we are connecting to a JMS queue.
Every day the first time we try to connect to the JMS queue it is throwing the following exception:
javax.jms.JMSException: MQJMS2008: failed to open MQ queue <queue name>
But the subsequent calls are executing successfully without any issues.
Can someone please guide me as to what the problem could be from a configuration perspective. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 06, 2009 1:38 am Post subject: Re: MQJMS2008: failed to open MQ queue exception |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| msvpraveen wrote: |
| Can someone please guide me as to what the problem could be from a configuration perspective. |
Without the linked exception with a reason code it's guesswork, but my first instinct is something in your network timed out/quiecsed that doesn't come up fast enough for the connect to succeed and gives you a 2059.
If that's the case, ask the network admins if there's anything likely to behave like that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| msvpraveen |
| Posted: Mon Apr 06, 2009 5:37 am Post subject: |
|
|
Novice
Joined: 07 Jul 2005
Posts: 12
|
Well if it was truly a network problem it would have occured more than once and not just the first time every day (irrespective of time).
Thats what we couldn't understand. The only exception that is being thrown to us is that the queue couldn't be opened the first time. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Mon Apr 06, 2009 7:10 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
This situation has been discussed before, where an application has to "try twice" to get its first connection of the day. As Vitor says, you need a linked exception to give a useful MQ reason code.
In the absence of a reason code, it may be that your connection is being dropped overnight (a firewall timeout for inactivity is one hypothesis). See this:
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21229508
Of course, this is useless advice if I've guessed the reason code incorrectly. For proper linking of exceptions, try this:
http://www.mqseries.net/phpBB2/viewtopic.php?t=42149 |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 06, 2009 7:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| msvpraveen wrote: |
| Well if it was truly a network problem it would have occured more than once and not just the first time every day (irrespective of time). |
And if it was truly a configuration problem it would happen everytime.
| msvpraveen wrote: |
| The only exception that is being thrown to us is that the queue couldn't be opened the first time. |
The first time, or the first time each day / after a considerable period of inactivity? There is a difference.
If the application has been left running, it's possible that it's trying to use a connection that's been timed out by a network element.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
