| Author |
Message
|
| skydoor |
 Posted: Thu Dec 18, 2008 11:29 pm Post subject: Corrupt queue |
 |
|
Apprentice
Joined: 24 Jul 2007
Posts: 43
Location: Cape Town
|
All,
I had a problem with a queue.
When the client tried to access it, it first threw "MQJE001: Completion Code 2, Reason 2195". When I tried to access it via rfhutil it said "Main storage unavailable". I then restarted the queue manager and it then threw "2101 MQRC_OBJECT_DAMAGED". I could not do a media recovery as my queue manager was not set up to allow media recoveries. I then deleted the queue and recreated it. I would like to know why this happened, and if it might have something to do with SAN storage? .
Please see below the version, errors that was logged and the queue definition.
C:\Documents and Settings\mq>dspmqver
Name: WebSphere MQ
Version: 6.0.2.0
CMVC level: p600-200-060921
BuildType: IKAP - (Production)
AMQ8409: Display Queue details.
QUEUE(NAME REMOVED) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2008-12-19)
ALTTIME(07.36.53) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER(NAME REMOVED) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2008-12-19) CRTIME(03.33.06)
CURDEPTH(0) DEFBIND(NOTFIXED)
DEFPRTY(0) DEFPSIST(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ( ) IPPROCS(10)
MAXDEPTH(5000) MAXMSGL(104857600)
MONQ(QMGR) MSGDLVSQ(PRIORITY)
NOTRIGGER NPMCLASS(NORMAL)
OPPROCS(2) PROCESS( )
PUT(ENABLED) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(999999999)
RETINTVL(999999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA( ) TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(FIRST)
USAGE(NORMAL)
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri December 19 03:22:57 South Africa Standard Time 2 |
| Host Name :- NAME REMOVED (Windows Ver 5.2 Build 3790: Service Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- AQ123002 |
| Application Name :- MQM |
| Component :- aqqLoadMsgHdr |
| SCCS Info :- lib/lqm/amqaqqoa.c, 1.25.1.1 |
| Line Number :- 382 |
| Build Date :- Sep 21 2006 |
| CMVC level :- p600-200-060921 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\IBM\WebSphere MQ\bin\amqzlaa0.exe |
| Addressing mode :- 32-bit |
| Process :- 00001232 |
| Thread :- 00000002 |
| QueueManager :- NAME REMOVED |
| ConnId(1) IPCC :- 190 |
| ConnId(2) QM :- 38 |
| Major Errorcode :- arcE_OBJECT_DAMAGED |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri December 19 03:20:52 South Africa Standard Time 2 |
| Host Name :- ZACTWMQ3 (Windows Ver 5.2 Build 3790: Service Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XY205001 |
| Application Name :- MQM |
| Component :- xstConnectionRequest |
| SCCS Info :- lib/cs/pc/winnt/amqxstpn.c, 1.18.1.2 |
| Line Number :- 450 |
| Build Date :- Sep 21 2006 |
| CMVC level :- p600-200-060921 |
| Build Type :- IKAP - (Production) |
| UserID :- mq |
| Process Name :- c:\ibm\wa\AdapterJRE\bin\java.exe |
| Addressing mode :- 32-bit |
| Process :- 00004824 |
| Thread :- 00000004 |
| QueueManager :- QMPROCESS1 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Failed to complete request to Shared Storage Server) |
| FDCSequenceNumber :- 1 |
| Comment1 :- Failed to complete request to Shared Storage Server |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri December 19 03:20:52 South Africa Standard Time 2 |
| Host Name :- ZACTWMQ3 (Windows Ver 5.2 Build 3790: Service Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XC371020 |
| Application Name :- MQM |
| Component :- xstServerRequest |
| SCCS Info :- lib/cs/pc/winnt/amqxstpn.c, 1.18.1.2 |
| Line Number :- 659 |
| Build Date :- Sep 21 2006 |
| CMVC level :- p600-200-060921 |
| Build Type :- IKAP - (Production) |
| UserID :- mq |
| Process Name :- c:\ibm\wa\AdapterJRE\bin\java.exe |
| Addressing mode :- 32-bit |
| Process :- 00004824 |
| Thread :- 00000004 |
| QueueManager :- QMPROCESS1 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Subpool Server 1 pid[4292] has terminated while application connected.) |
| FDCSequenceNumber :- 0 |
| Arith2 :- 4292 10c4 |
| Comment1 :- Subpool Server 1 pid[4292] has terminated while |
| application con |
| |
+-----------------------------------------------------------------------------+
[/i]
_________________
The answer to the question is 42 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Dec 18, 2008 11:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks like somebody brutally killed a qmgr process while the java app was processing something on the object. ...
If the qmgr was normally shutdown make sure that the java app uses the option FAIL_IF_QUIESCE. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| faustus |
| Posted: Tue Feb 17, 2009 5:37 am Post subject: |
|
|
Novice
Joined: 29 Apr 2008
Posts: 12
|
yes it seem so, i have actually the same errors after hard kill a qmgr. what can i do for resolving the problem?
thanks Faustus |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 17, 2009 5:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| faustus wrote: |
what can i do for resolving the problem?
|
Make sure applications are coded to close when the queue manager signals a shutdown, and make sure you've exhausted all other options before shooting the queue manager right in the processes.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| friedl.otto |
| Posted: Tue Feb 17, 2009 6:58 am Post subject: |
|
|
Centurion
Joined: 06 Jul 2007
Posts: 116
|
| Vitor wrote: |
| ...and make sure you've exhausted all other options before shooting the queue manager right in the processes. |
Hmmm, I'm thinking this sig material! 
_________________
Here's an idea - don't destroy semaphores unless you're certain of what you're doing!  -- Vitor |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 17, 2009 7:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| friedl.otto wrote: |
| Vitor wrote: |
| ...and make sure you've exhausted all other options before shooting the queue manager right in the processes. |
Hmmm, I'm thinking this sig material! |
Well yes, we have discussed this is the past have we not? 
The point, to spell it out for future readers, is that queue managers should always be brought down by means of the endmqm command and it's various options. Using OS faciltities to bring down queue manager processes should be considered a last resort, performed only as described in the System Administration manual and with the expectation that things might wobble a bit afterwards.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| friedl.otto |
| Posted: Tue Feb 17, 2009 9:52 am Post subject: |
|
|
Centurion
Joined: 06 Jul 2007
Posts: 116
|
For the terminally lazy (and or cerebrally challenged) ...
| Vitor wrote: |
| The point, to spell it out for future readers, is that queue managers should always be brought down by means of the endmqm command and it's various options. |
Windows & UNIX
i5/OS
| Vitor wrote: |
| Using OS faciltities to bring down queue manager processes should be considered a last resort, performed only as described in the System Administration manual and with the expectation that things might wobble a bit afterwards. |
Windows
UNIX
i5/OS
_________________
Here's an idea - don't destroy semaphores unless you're certain of what you're doing! -- Vitor |
|
| Back to top |
|
|
| yhuang |
| Posted: Mon May 18, 2009 7:40 am Post subject: Could you please let me know how to fix it? |
|
|
Newbie
Joined: 03 Feb 2009
Posts: 5
|
Hi,
I am having the same problem now. Could you please let me know how to fix it?
Thanks,
Yun
| faustus wrote: |
yes it seem so, i have actually the same errors after hard kill a qmgr. what can i do for resolving the problem?
thanks Faustus |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 18, 2009 8:56 am Post subject: Re: Could you please let me know how to fix it? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yhuang wrote: |
I am having the same problem now. Could you please let me know how to fix it?
|
Follow the advice in this thread, especially the links helpfully provided in the previous post. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gunter |
| Posted: Mon May 18, 2009 11:48 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
|
| Back to top |
|
|
|
|
