| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| QMGR issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| vam |
 Posted: Tue Feb 14, 2012 9:27 am Post subject: QMGR issue |
 |
|
Acolyte
Joined: 16 Mar 2010
Posts: 70
|
Queue Manager went down:
Suddenly one of our queue manager went down in production.the below is the error log:
WebSphere MQ First Failure Symptom Report
=========================================
Date/Time :- Wednesday November 23 12:57:20 EST 2011
Host Name :- w09a2130 (HP-UX B.11.23)
PIDS :- 5724H7202
LVLS :- 6.0.2.0
Product Long Name :- WebSphere MQ for HP-UX (PA-RISC platform)
Vendor :- IBM
Probe Id :- XY086003
Application Name :- MQM
Component :- xllOSSpinLockWaitLock
SCCS Info :- lib/cs/unix/hp700_ux90/amqxlosl.c, 1.2.12.1
Line Number :- 375
Build Date :- Sep 21 2006
CMVC level :- p600-200-060921
Build Type :- IKAP - (Production)
UserID :- 00008010 (mqm)
Program Name :- amqrmppa_nd
Addressing mode :- 64-bit
Process :- 7759
Thread :- 213723
QueueManager :- LZG.PROD.A
ConnId(1) IPCC :- 1740186
Major Errorcode :- xecL_W_LONG_LOCK_WAIT
Minor Errorcode :- OK
Probe Type :- MSGAMQ6150
Probe Severity :- 3
Probe Description :- AMQ6150: WebSphere MQ semaphore is busy.
FDCSequenceNumber :- 0
Error Log Info:
----- amqxfdcx.c : 805 --------------------------------------------------------
01/16/11 08:30:24 - Process(4046.1) User(mqm) Program(amqzmgr0)
AMQ6125: An internal WebSphere MQ error has occurred.
EXPLANATION:
An internal error has occurred with identifier 10805014. This message is
issued in association with other messages.
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.
----- amqxfdcx.c : 766 --------------------------------------------------------
01/16/11 08:30:24 - Process(4046.1) User(mqm) Program(amqzmgr0)
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
LZG.PROD.A
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 4046.
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
-----------------------------------------------------------------------------
Once we got similar issue in dev box and then we increased the primary and secondary log files of the queue manager.
Is is the same issue as per the above log ? Please suggest. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Feb 14, 2012 9:50 am Post subject: Re: QMGR issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vam wrote: |
Once we got similar issue in dev box and then we increased the primary and secondary log files of the queue manager.
Is is the same issue as per the above log ? Please suggest. |
Probably; I doubt it's the root cause. I would suspect you have some application that's not playing nice; take a look at this and see if it's relevant.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 14, 2012 9:51 am Post subject: Re: QMGR issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vam wrote: |
| LVLS :- 6.0.2.0 |
This probably isn't helping much either.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Feb 14, 2012 3:02 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
Could be due to a hung process or 100% CPU busy for a long time or a HP-UX OS glitch. Think about raising a PMR if it happens again. This sort of thing is very rare.
_________________
Glenn |
|
| Back to top |
|
|
| JasonE |
| Posted: Thu Feb 16, 2012 5:08 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
When you see xecL_W_LONG_LOCK_WAIT FDC's it means you've waited longer than a certain time to get a lock. This is usually followed by another FDC later on when the person who owns the lock releases it, so you can see what it was doing. If you are not seeing the second, chances are its a deadlock which will never resolve itself, and would need investigation by IBM.
That's nearly 6 years old, and there's lots and lots of issues fixed. Apply maintenance first! |
|
| 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
|
|
|
|
