| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Getting return code 2059 although queue manager is running |
« View previous topic :: View next topic » |
| Author |
Message
|
| hilltops |
 Posted: Mon Nov 27, 2006 8:02 am Post subject: Getting return code 2059 although queue manager is running |
 |
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
I have got a queue manager which appears to be up and running but would not accept connections from client applications. The applications connect over server connections channels and the queue manager gets into this error situations after about 14 days of functionality mormally.
The queue manager is a cluster member and when it starts erroring the channels to/from the repository queue channels go into a retry state. I am running MQ 6.0.1.1 on linux.
The application is written in standard java (not JMS) and the application is explicitly disconnecting from the queue manager as in;
try
{
qManager.disconnect();
}
catch (Exception e)
{
System.out.println("Couldn't disconnect from QManager: " + e);
}
I suppect although the application is disconnecting, its handle to the MQ agent process may not have been released. Is there a way of checking this.
I have done a ps -ef | grep amqzlaa0 and found the following;
mqm 32346 32308 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32355 32346 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32356 32355 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32358 32355 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32359 32355 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32360 32355 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32361 32355 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32362 32355 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32368 32355 0 14:49 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32417 32308 0 14:50 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 32418 32417 0 14:50 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 32419 32418 0 14:50 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 32420 32418 0 14:50 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 32421 32418 0 14:50 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 32481 32418 0 14:51 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 32616 32355 0 14:57 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip0
mqm 32631 32418 0 14:58 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 32658 32418 0 14:59 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 317 32418 0 15:01 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 329 32418 0 15:01 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip1
mqm 1712 32308 0 15:37 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip67
mqm 1713 1712 0 15:37 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip67
mqm 1714 1713 0 15:37 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip67
mqm 1715 1713 0 15:37 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip67
mqm 1716 1713 0 15:37 ? 00:00:00 amqzlaa0 -mLSLAK09CPS -fip67
I have just re-cycled the queue manager and everything seem OK now but am sure the problem will crop up again in about 12-15 days time. I want to subject the queue manager under some degree of monitoring, hence my question. What should I be looking out for?
Thankx |
|
| Back to top |
|
 |
| xxx |
| Posted: Mon Nov 27, 2006 9:08 am Post subject: |
|
|
Centurion
Joined: 13 Oct 2003
Posts: 137
|
I guess you don't need to recycle the Qmanager,
You need to find the actual Cause of it , dis chs(*) should help you , see if there are any applications that are not closing the connections properly, |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Mon Nov 27, 2006 9:38 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
Where amqzlaa0 is a process meant for queue manager agents.
I think your application is not cleaning the mq connections properly
please re-check it once again
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| hilltops |
| Posted: Tue Nov 28, 2006 3:55 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
| The application has definitely issued the qmgr.disconnect() command (I ahve got access to the code and I have checked it). When I run the command dis chs(*) on the queue manager, I do not see the channel running; other clustered channel are running, the the server conn is not. Is there any other way of checking if the application has disconnected cleanly? |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Nov 28, 2006 5:19 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
If you don't mind, will you please tell me how the qmgr.disconnect() works and what is there in that funtion.
if you can post it here, we will have a look on that.
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| 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
|
|
|
|
