| Author |
Message
|
| Pablo Taboada |
 Posted: Wed Feb 13, 2008 5:31 am Post subject: Error => MQJMS2008: failed to open MQ queue |
 |
|
Apprentice
Joined: 19 Jul 2007
Posts: 36
Location: Spain - Barcelona
|
Hi,
I have an application (fem) that run under WAS (WebSphere Application Server) and connected to WebSphere MQ.
The problem is that sometimes, I obtain next error:
[2008-02-13 14:23:20,430] Thread-44017 es.lacaixa.fem.listener.mqseries.FusionYAlmacenamientoLector FATAL - Se ha producido un error crÃtico (Critical error has been happened). # MQJMS2008: failed to open MQ queue
Interesting Data:
WAS version: v6.0.2.15
WMQ version: v6.0.2.1
OS: AIX 5.3
[hostname].root:/ > oslevel -g
Fileset Actual Level Maintenance Level
-----------------------------------------------------------------------------
bos.rte 5.3.0.50 5.3.0.0
anyone can help me?
A lot of thanks!!
_________________
Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Feb 13, 2008 5:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There should be an MQ Return Code (MQRC) with that error message.
If not, you need to change your code to report it by reporting on the LinkedException.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Pablo Taboada |
| Posted: Wed Feb 13, 2008 5:55 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007
Posts: 36
Location: Spain - Barcelona
|
I don't have any Return Code (MQRC).
Does it want to say that maybe it is not because of WebSphere MQ problem?
That's to say... It's posible that it is a programming (development) issue?
_________________
Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 13, 2008 6:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm saying that without the MQRC, if that's the full exception reported, then there's no way to know what's going on.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 13, 2008 6:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Pablo Taboada wrote: |
I don't have any Return Code (MQRC).
Does it want to say that maybe it is not because of WebSphere MQ problem?
|
Do you mean there's no linked exception? A bit odd - experience teaches that a MQJMS2008 is typically produced when a JMS app tries to open a queue and something goes wrong. The "something" being in the linked exception.
But my knowledge of Java is famed for it's brevity.
It's perfectly possible that the root cause of the problem is application based - a 2085 generated because the application's spelt the name wrongly. But that would still have a linked exception with a 2085.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Pablo Taboada |
| Posted: Wed Feb 13, 2008 6:14 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007
Posts: 36
Location: Spain - Barcelona
|
Hi Vitor,
My java knowledgements are so badly  but, in WMQ error logs doesn't apperar error messages. The only error messages are in WAS- FEM error logs. By the other hand, this error is not always present in error logs. That's to say, sometimes runs right and sometimes runs wrong.
The problem is that I'm not make developement of this application, I'm only WMQ administrator, and I'm starting to administrate WAS.
_________________
Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 13, 2008 6:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Pablo Taboada wrote: |
| in WMQ error logs doesn't apperar error messages. The only error messages are in WAS- FEM error logs. By the other hand, this error is not always present in error logs. That's to say, sometimes runs right and sometimes runs wrong. |
Not all application errors are reported in the logs; the 2085 example I quoted wouldn't be, that's just passed back to the program. If they're getting a 2009/2019 sort of thing, then the nature of the error is that the queue manager might log it.
But without the information passed back to the application, any attempt at resolution is guesswork.
| Pablo Taboada wrote: |
| The problem is that I'm not make developement of this application |
Then it's not your problem. Push back on whoever is developing the application and tell them it's a code problem unless they can prove it's an MQ issue with a linked exception proving it is.
Sorted. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Pablo Taboada |
| Posted: Wed Feb 13, 2008 7:56 am Post subject: |
|
|
Apprentice
Joined: 19 Jul 2007
Posts: 36
Location: Spain - Barcelona
|
Ok Vitor,
A lot of thanks. I'll tall with development department. 
_________________
Regards,
Pablo Taboada
INSA - IBM Global Services
WebSphere MQ System Administrator Certified |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 13, 2008 8:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Pablo Taboada wrote: |
| I'll tall with development department. |
That's the spirit - walk tall! 
Remember that to a developer, all problems are at least initially someone else's and MQ is an easy target.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Feb 17, 2008 9:22 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Vitor wrote: |
| Pablo Taboada wrote: |
| I'll tall with development department. |
That's the spirit - walk tall!
Remember that to a developer, all problems are at least initially someone else's and MQ is an easy target. |
Very true. |
|
| Back to top |
|
|
|
|
