| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| command server stopped |
« View previous topic :: View next topic » |
| Author |
Message
|
| KIT_INC |
 Posted: Mon Apr 25, 2016 9:16 am Post subject: command server stopped |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
Running MQ V8 on linux, the MQ errors log shows that the command server has stopped due to MQRC 2041 (object changed). The Object was SYSTEM.ADMIN.COMMAND.QUEUE. Looking at the alteration date od the Q definition, there has been no changed since the Q was created. There is no alias Q used for the SYSTEM.ADMIN.COMMAND.QUEUE.
Does 2041 Object changed really means the change of the definition ? Is there any other changes that can result in 2041 ?
The error happens more than 10 days ago and the command server was left stopped until eventually some one noticed it. Should we be monitoring the command server in production ? Any suggestion ? |
|
| Back to top |
|
 |
| hughson |
| Posted: Tue May 03, 2016 1:22 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
I cannot think of any other reason that would contribute a 2041 return code.
If there is, IBM should update the documentation to describe it.
Additionally, the command server is IBM code, and it should be following the behaviour expected by an application that receives a 2041, which is to MQCLOSE and re-MQOPEN the queue again. It should not simply stop.
For these two reasons, I suggest you contact IBM by raising a PMR for this issue.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| 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
|
|
|
|
