| Author |
Message
|
| patkar.mahesh |
 Posted: Mon Aug 17, 2009 11:39 pm Post subject: Command Server not responding within timeout period. (AMQ403 |
 |
|
Novice
Joined: 22 Jan 2009
Posts: 11
|
Hi,
I am using MQ 6.0. I have 10 different local queues in one Queue manager. All of these queues have more than 50% current queue depth approx 50000 messages in each queue total approx 400000 messages in the queuemanager.
While refreshing the queue I am getting below error frequently, after this error if I close all the applications connected to MQ and tryied to stop the command server and start it again.
Error :
"Command Server not responding within timeout period. (AMQ4032)"
When I try to start the command server its shows
"AMQ8193: WebSphere MQ command server is ending."
for a long time...
Error log is updated as below message
----- amqxfdcp.c : 735 --------------------------------------------------------
8/18/2009 08:38:01 - Process(12280.530) User(MQ_ADMIN) Program(amqzlaa0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager XXXXX.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 12280.
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.
----- amqxfdcp.c : 773 --------------------------------------------------------
8/18/2009 09:28:00 - Process(12280.513) User(MQ_ADMIN) Program(amqzlaa0.exe)
AMQ6150: WebSphere MQ semaphore is busy.
EXPLANATION:
WebSphere MQ was unable to acquire a semaphore within the normal timeout period
of 0 minutes.
ACTION:
MQ will continue to wait for access. If the situation does not resolve itself
and you suspect that your system is locked then investigate the process which
owns the semaphore. The PID of this process will be documented in the
accompanying FFST.
----- amqxfdcp.c : 735 --------------------------------------------------------
8/18/2009 09:28:00 - Process(12280.513) User(MQ_ADMIN) Program(amqzlaa0.exe)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager XXXXXX.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 12280.
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.
----- amqxfdcp.c : 773 --------------------------------------------------------
Can anyone please give any solutions pls .... |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Aug 18, 2009 12:02 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Looks like a potential resource problem, but that's just a stab in the dark. Any FDC's cut?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 18, 2009 2:59 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You say you are using MQ 6.0 ... care to elaborate about the exact level?
Like 6.0.2.7 ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sumit |
| Posted: Tue Aug 18, 2009 6:21 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| exerk wrote: |
| Looks like a potential resource problem, but that's just a stab in the dark. |
Indeed, looks like resource problem atleast after this error
| Quote: |
----- amqxfdcp.c : 773 --------------------------------------------------------
8/18/2009 09:28:00 - Process(12280.513) User(MQ_ADMIN) Program(amqzlaa0.exe)
AMQ6150: WebSphere MQ semaphore is busy.
EXPLANATION:
WebSphere MQ was unable to acquire a semaphore within the normal timeout period
of 0 minutes.
ACTION:
MQ will continue to wait for access. If the situation does not resolve itself
and you suspect that your system is locked then investigate the process which
owns the semaphore. The PID of this process will be documented in the
accompanying FFST.
----- amqxfdcp.c : 735 -------------------------------------------------------- |
Check if your system has enough resource to help MQ work. You can try to end your queue manager, clear all semaphores and start it again so that qmgr can get fresh processes and enough space.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| gunter |
| Posted: Tue Aug 18, 2009 11:58 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
The queuemanager unloads queses if they are ot used. If this queue is used again, the queuemanager starts loading it. This may take a long time, depending on the queuedepth. In this time the queuemanager doesn't answers any request. If this has todo with your problem, you should find related entries in AMQERR01.LOG.
MQ is not intended and not optimized to hold a big amout of messages.
It's not a bug, it's a feature. 
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Aug 19, 2009 6:01 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| gunter wrote: |
| The queuemanager unloads queses if they are ot used. If this queue is used again, the queuemanager starts loading it. This may take a long time, depending on the queuedepth. In this time the queuemanager doesn't answers any request. If this has todo with your problem, you should find related entries in AMQERR01.LOG. |
Huh? Where did you read that? Queue managers don't unload or load queues, unless its recovering from a failure by reading the logs.
| Quote: |
| MQ is not intended and not optimized to hold a big amout of messages. |
I think IBM would strongly disagree with that.
_________________
Glenn |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Aug 19, 2009 6:06 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Load a queue up with several tens of thousands of messages.
Leave it unaccessed (not open for anything, even MQINQ) for a while.
MQOPEN it. Watch the clock as the seconds tick by. Look in the QM error log for all the "QM is loading the queue" messages, one for every 10,000 messages.
I opened a PMR on this. They said this was always the behaviour, just that MQ 6.0 added those messages to the QM error log to show what's happening.
I dunno. I don't remember queues with tens of thousands of messages taking seconds upon seconds to open at MQ 5.3, but OK.
(Please, no replies saying a queue shouldn't have a lot of messages. The fact is that some queues sometimes do!)
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 19, 2009 8:24 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
The folks at the MQ factory assume that a msg MQPUT will be quickly MQGETed (MQGOTTEN? what the heck is the past tense of MQGET...), so I'm thinking that load here means moving from buffer to disk.
_________________
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 |
|
|
|
|
