| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Error: MQJE001: Completion Code 2, Reason 2042 |
« View previous topic :: View next topic » |
| Author |
Message
|
| MQFard |
 Posted: Fri Sep 09, 2005 12:03 pm Post subject: MQ Error: MQJE001: Completion Code 2, Reason 2042 |
 |
|
Novice
Joined: 07 Oct 2004
Posts: 17
Location: VSP.COM
|
Has anyone seen this error before? We are using a model queue for our agent desktop application, which has been working fine for several months. Today we received this error. I know it’s a share/exclusive issue but I’m a little confused. The default for the model queue definition is exclusive. Does anyone know why? Also the application worked fine with the exclusive for several months. The following is the full application error log text:
2005-09-08 07:50:38,385 (Thread - 2399) exception=0; com.vsp.enterprise.services.queuemessaging.QueueMessagingServices got Exception: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
com.ibm.ejs.container.UncheckedException: ; nested exception is:
com.vsp.arch.exception.QueueResourceException com.vsp.arch.exception.QueueResourceException: Queue ResourceException java.lang.Exception: MQJMS2008: failed to open MQ queue -- MQ Error: MQJE001: Completion Code 2, Reason 2042
Thanks,
MQFard |
|
| Back to top |
|
 |
| kman |
| Posted: Wed Sep 14, 2005 11:00 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
The default definition is taken from SYSTEM.DEFAULT.MODEL.QUEUE if not specified otherwise during the model queue definition.
There could be a rogue application or an abnormal running application that is holding on the model queue without your knowledge. |
|
| Back to top |
|
|
| MQFard |
| Posted: Thu Sep 15, 2005 10:33 am Post subject: Thanks for the info. |
|
|
Novice
Joined: 07 Oct 2004
Posts: 17
Location: VSP.COM
|
We cycled our WAS server and the issue cleared. We still don't know why it occured.
_________________
To Fard
WebSphere MQ Administrator |
|
| Back to top |
|
|
| hopsala |
| Posted: Thu Sep 15, 2005 10:59 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
I believe what probably happened is as such: your application went up, opened the queue, worked for a while and then crashed for some irrelevant reason. Afterwards, when you tried re-opening the queue, you got a 2042 since MQ had yet found out that the appl crashed before, and thinks the queue is still open.
Concerning the "why the default is such and such" question, note that most mq object defaults are a long way from making any sense - DEFPSIST(NO), a long retry int that takes years, and there are many other such examples. Every self-respecting admin should keep a default-modification script in his arsenal, and use it whenever creating a new qm (saveqmgr is your friend...) |
|
| 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
|
|
|
|
