| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Deleting a queue with process attached? |
« View previous topic :: View next topic » |
| Author |
Message
|
| shashivarungupta |
 Posted: Sat Oct 26, 2013 11:23 pm Post subject: |
 |
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Similar issue has resurfaced again on MQv6.0.2.6 and it was related to Command Server Process again. Even after starting the Qmgr ..there was an issue with Command Server Process and Qmgr was restarted to resolve it.
We've raised a PMR with vendor to get to know , the cause of this issue.. which has hit again.
Some of the Error logs are as follows (there are few more errors in the log).
I've not yet get the Root Cause of why the Command Server Process is behaving like this , when Qmgr is running and suddenly Command Server Process vanishes from the process state table.
| Quote: |
10/26/2013 10:36:50 PM - Process(21686.5) User(mqm) Program(amqzmur0)
AMQ6090: WebSphere MQ was unable to display an error message 7D9.
EXPLANATION:
MQ has attempted to display the message associated with return code hexadecimal
'7D9'. The return code indicates that there is no message text associated with
the message. Associated with the request are inserts 0 : 0 : : : .
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
|
| Quote: |
----- amqxfdcx.c : 807 --------------------------------------------------------
10/26/2013 10:37:18 PM - Process(21686.1) User(mqm) Program(amqzmur0)
AMQ6090: WebSphere MQ was unable to display an error message 7D9.
EXPLANATION:
MQ has attempted to display the message associated with return code hexadecimal
'7D9'. The return code indicates that there is no message text associated with
the message. Associated with the request are inserts 1 : 5 : STATISTICS : : .
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
|
| Quote: |
10/27/2013 02:16:20 AM - Process(5274.1) User(mqm) Program(amqzdmaa)
AMQ6119: An internal WebSphere MQ error has occurred ('22 - Invalid argument'
from semop.)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error
recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
|
Somewhere I suspect the issue with resources available at Kernel Level.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Oct 27, 2013 5:29 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
X'7d9' is decimal 2009. Lots of hits if you search google for mq+2009+command server.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bkiran2020 |
| Posted: Sun Oct 27, 2013 9:38 pm Post subject: |
|
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
|
| Back to top |
|
|
| roshan.171188 |
| Posted: Wed Oct 30, 2013 1:03 pm Post subject: |
|
|
Apprentice
Joined: 07 Jun 2012
Posts: 35
|
2009 + command server talks a lot about the symptoms and command server ending but I am still looking for the root cause.
I've noticed a similar problem on 7.0.1.3 as well.
Andy, You are correct, Once the agent controller process ends, and then the command server process, MQ is unable to take precautions which leaves an orphan process attached to the command queue which does not exist on the system level.
Lets take my initial question (to resolve this problem without a queue manager restart) out of the picture, and focus currently on the cause of processes terminating on the first place.
I can see from the logs that says the agent controller process was not found and is expected to be terminated either by a user or my the system.
User terminating the process is out of the question.
And if OS is killing the processes to free up system resources, is there a way to track it? |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Thu Oct 31, 2013 1:03 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| roshan.171188 wrote: |
| 2009+ command server talks a lot about the symptoms and command server ending.... |
Agree...
| roshan.171188 wrote: |
| Once the agent controller process ends, and then the command server process, MQ is unable to take precautions which leaves an orphan process attached to the command queue which does not exist on the system level. |
as per the design of MQ.. any changes at Kernel level, if those are short of vendor recommended values.. MQ would be one of the first applications to get affected cause of those.
| roshan.171188 wrote: |
I can see from the logs that says the agent controller process was not found and is expected to be terminated either by a user or my the system.
...if OS is killing the processes to free up system resources, is there a way to track it? |
Apart from that question, is there a way to prevent unexpected killing of MQ Processes.. ( apart from imposing the ibm recommended resources at kernel level )
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Oct 31, 2013 4:45 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| shashivarungupta wrote: |
| ... is there a way to prevent unexpected killing of MQ Processes.. ( apart from imposing the ibm recommended resources at kernel level ) |
No, not really. If you fail to adequately provision the server, then applications will experience unexpected results.
There is little WMQ can do to recover from insufficient resources (RAM, disk space, o/s resources).
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
