| Author |
Message
|
| migcr |
 Posted: Tue Dec 28, 2004 6:56 am Post subject: An MQSeries error occurred : Completion code 2 Reason code 2 |
 |
|
Novice
Joined: 22 Apr 2003
Posts: 12
|
Hi,
first, i apologize for my english.
We have a strange problem with the MQseries. We can´t send/receive messages from our queue manager. Every time we try to put a message in a queue, with a java client, we get the following error messages:
----------------------
Unable to load message catalog - mqji
An MQSeries error occurred : Completion code 2 Reason code 2059
----------------------
We also have problems with runmssc, because when we get into the "console" no command works. It gets hanged.
Actually, the endmqm commad doesn´t work and it gets hanged, also.
Thanks,
Miguel |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Dec 28, 2004 7:13 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
2059 means queue manager not available. You said that you were using a java client. Places to look for problems are:
- the environment for the java program (ie, the channel, port, hostname)
- the queue manager name that you are using
- is your listener running on your server (and is it running on the port you specify in your java program)
The mqji error won't affect your program. If you search on it here, you'll find the hits on how to update your classpath to get rid of it.
I'm not sure that I understand your hang problems. I've never seen them myself. Are you getting any errors or FDCs produced with them? Also, what operating system and version of WMQ are you using? |
|
| Back to top |
|
|
| migcr |
| Posted: Tue Dec 28, 2004 7:59 am Post subject: |
|
|
Novice
Joined: 22 Apr 2003
Posts: 12
|
The dspmq command says that the queue manager is running, and the listener is also up.
The configuration of the client (queue manager, channel, queue...) are rigth because they hasn´t been changed, and they worked before.
We are using MQSeries 5.2 on HP-UX 11.11.
thanks a lot,
Miguel. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 28, 2004 8:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| migcr wrote: |
| The configuration of the client (queue manager, channel, queue...) are rigth because they hasn´t been changed, and they worked before. |
Before what?
What was changed?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| migcr |
| Posted: Tue Dec 28, 2004 8:09 am Post subject: |
|
|
Novice
Joined: 22 Apr 2003
Posts: 12
|
That´s my problem. I suspect that someone changed something, because a week ago everything worked fine.
Any suggestion?What can i check?
kind regards,
Miguel. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Dec 28, 2004 8:18 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Any suggestion?What can i check? |
What makes you think your listener is running? How did you check?
If it is, then is it listening on the port number you specified in your java mq client program? |
|
| Back to top |
|
|
| migcr |
| Posted: Tue Dec 28, 2004 8:44 am Post subject: |
|
|
Novice
Joined: 22 Apr 2003
Posts: 12
|
i check it with the ps comand, and wiht netstat.
ps shows that the process runmqls is running, and netstat shows the port of the listener is listening.
kind regards,
Miguel |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Dec 28, 2004 9:00 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| migcr |
| Posted: Wed Dec 29, 2004 12:58 am Post subject: |
|
|
Novice
Joined: 22 Apr 2003
Posts: 12
|
I finally decided to kill al the processes and free all the resources. Then i started again the mq manager and it seems that it works now.
kind regards,
Miguel |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 29, 2004 1:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I've had the case once. Everything seemed to be working ok, even the listener.
WRONG -- the listener was not started by the right id (mqm or id in mqm grp) but by root.
The system behaved as if no listener had been running.
Quite strange isn't it ?
Enjoy  |
|
| Back to top |
|
|
|
|
