| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| What is the reason for a qmgr that is down? |
« View previous topic :: View next topic » |
| Author |
Message
|
| rram75 |
 Posted: Thu Jan 08, 2004 1:37 am Post subject: What is the reason for a qmgr that is down? |
 |
|
Newbie
Joined: 08 Jul 2002
Posts: 4
Location: India
|
Dear All,
Today i noticed my qmgrs went down for unknown reasons.
When i use, dspmq cmd in /opt/mqm/bin it shows as below.
QMNAME(SGCCT_QM.DV) STATUS(Ended unexpectedly)
By looking in to the logs at /var/mqm/qmgrs/SGCCT_QM!DV/errors/ directory
below is the msg i could see.
1)AMQ9510: Messages cannot be retrieved from a queue.
EXPLANATION:
The attempt to get messages from queue 'SYSTEM.CHANNEL.INITQ' on queue manager
'SGCCT_QM.DV' failed with reason code 2009.
ACTION:
If the reason code indicates a conversion problem, for example
MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise,
ensure that the required queue is available and operational.
2)01/08/04 12:55:00 PM
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'SGCCT.SGPIMS' ended abnormally.
ACTION:
Look at previous error messages for channel program 'SGCCT.SGPIMS' in the error
files to determine the cause of the failure.
Can any one advise me the reason for the qmgr's went down.
What will be status shown while using dspmq cmd , if a qmgr was shutdown using endmqm.
Many thanks in Advance |
|
| Back to top |
|
 |
| kman |
| Posted: Thu Jan 08, 2004 2:03 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
If you use endmqm the status would be 'Ended normally'. endmqm -i would give 'Ended immediately'
| Quote: |
QMNAME(CQM1) STATUS(Ended normally)
QMNAME(QM1) STATUS(Ended normally)
QMNAME(QM2) STATUS(Ended normally)
QMNAME(QM3) STATUS(Ended normally)
QMNAME(TQM) STATUS(Ended unexpected
ly)
QMNAME(TQM2) STATUS(Ended immediatel
y) |
The reason for queue manager went down could be due to many things. If it was not ended manually, then there should be something reported in the error log, and associated with it an FDC file. Take a look in the error directory if you have any FDCs. Somethinf like,
| Quote: |
AMQ6118: An internal WebSphere MQ error has occurred (20806823)
EXPLANATION:
An error has been detected, and 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.
AMQ6184: An internal WebSphere MQ error has occurred on queue manager TQM.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 1536.
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.
|
In this example, there should be 1536.FDC file. |
|
| Back to top |
|
|
| rram75 |
| Posted: Thu Jan 08, 2004 2:48 am Post subject: |
|
|
Newbie
Joined: 08 Jul 2002
Posts: 4
Location: India
|
Hi,
In FDC files no error msg is found for today's date.
I looked FDC files at /var/mqm/errors directory. Is it right to check here?? |
|
| Back to top |
|
|
| kman |
| Posted: Thu Jan 08, 2004 7:34 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
The FDCs should be in /var/mqm/errors. Look for the file name AMQnnnn.mm.FDC, where nnnn would be the process id that was failing. It may not be on the date you are looking at, but must correspond to the failing process as caught in the error log.
Like in my example the failing process was 1536, so there should be AMQ1536.0.FDC in there, which woul dexplain the reason for the failure.
If no FDC was found and there was no failure mentioned or captured in the error log, then it'll be a bit more difficult to diagnose. You could start looking at the events in the syslogs to see what transpired before and during the time the queue manager was brought down - if not manually.  |
|
| 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
|
|
|
|
