MQSeries.net :: View topic - Probe ID: XY035010 (AMQ6125) ; xecL_E_NOT

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Probe ID: XY035010 (AMQ6125) ; xecL_E_NOT_OWNER

Probe ID: XY035010 (AMQ6125) ; xecL_E_NOT_OWNER

« View previous topic :: View next topic »

Author

Message

Gilly

Posted: Thu Nov 25, 2004 2:59 am Post subject: Probe ID: XY035010 (AMQ6125) ; xecL_E_NOT_OWNER

Novice

Joined: 27 Jul 2004
Posts: 10
Location: UK

Hi,
We hit MQ problems on a W2K server that we've not seen before. We are using 5.3 with CSD07. The header of the FDC shows the following, but I've had no joy searching the IBM support for this.
Gilly

+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon November 22 22:45:22 GMT Standard Time 2004 |
| Host Name :- UKFAWL02 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XY035010 |
| Application Name :- MQM |
| Component :- xllSpinLockRelease |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- UKMQserv |
| Process Name :- F:\IBM\WebSphere MQ\bin\amqhasmn.exe |
| Process :- 00001416 |
| Thread :- 00000001 |
| QueueManager :- UKFAWS1P02 |
| Major Errorcode :- xecL_E_NOT_OWNER |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
AMQHASMX main
mqlpgasn
mqlpgwlp2
xllSpinLockRelease
xcsFFST

sjensen

Posted: Thu Nov 25, 2004 4:51 am Post subject:

Centurion

Joined: 18 Dec 2003
Posts: 134
Location: London

Hi,

What are you trying to do when the FDC is thrown?

There is some info here: http://www-1.ibm.com/support/docview.wss?uid=swg21035567

not sure if it is relevant.

Good luck

Stefan

Gilly

Posted: Thu Nov 25, 2004 6:33 am Post subject:

Novice

Joined: 27 Jul 2004
Posts: 10
Location: UK

Stefan,

Thank you for your reply. To be honest, I don't know what was going on at the time of the problem. I was notified when a system administrator reported that MQ was not running and that he could not start the service.

The problem has only happened once, and although we've not seen it since we'd prefer to follow up before it comes back to haunt us.

Gilly

JasonE

Posted: Mon Nov 29, 2004 5:17 am Post subject:

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

Just to confirm there are no other fdcs cut around the same time?

The times I can find reports of this they are pretty much unexplained other than when there is a preceeding error usually caused by MQ trying to update log files while things like backup or antivirus software is reading them.

Gilly

Posted: Mon Nov 29, 2004 9:06 am Post subject:

Novice

Joined: 27 Jul 2004
Posts: 10
Location: UK

Hi Jason.
There are more FDC files, but I wasn't sure which were cause and which were effect, so I sent the first FDC referred to in the event log. Here are the headers from the other files.

This refers to a failed process:

| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon November 22 23:08:38 GMT Standard Time 2004 |
| Host Name :- UKFAWL02 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX005020 |
| Application Name :- MQM |
| Component :- zxcProcessChildren |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- UKMQserv |
| Process Name :- F:\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Process :- 00001288 |
| Thread :- 00000001 |
| QueueManager :- UKFAWS1P02 |
| Major Errorcode :- zrcX_PROCESS_MISSING |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ5008 |
| Probe Severity :- 2 |
| Probe Description :- AMQ5008: An essential WebSphere MQ process 1660 cannot |
| be found and is assumed to be terminated. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1660 67c |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zxcProcessChildren
xcsFFST

An unexpected os error:

WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon November 22 23:08:33 GMT Standard Time 2004 |
| Host Name :- UKFAWL02 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- HL006003 |
| Application Name :- MQM |
| Component :- hlgWriteLogRecord |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- UKMQserv |
| Process Name :- F:\IBM\WebSphere MQ\bin\amqzllp0.exe |
| Process :- 00001660 |
| Thread :- 00000001 |
| QueueManager :- UKFAWS1P02 |
| Major Errorcode :- hrcE_MQLO_UNEXPECTED_OS_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zllpMain
alsCheckPointLoop
aocPerformCheckpoint
almBeginCheckPoint
almLogIt
hlgWriteLogRecord
xcsFFST

An internal websphere error:

| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon November 22 22:45:23 GMT Standard Time 2004 |
| Host Name :- UKFAWL02 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- HL006005 |
| Application Name :- MQM |
| Component :- hlgWriteLogRecord |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- UKMQserv |
| Process Name :- F:\IBM\WebSphere MQ\bin\amqzlaa0.exe |
| Process :- 00001844 |
| Thread :- 00000007 |
| QueueManager :- UKFAWS1P02 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- hrcE_MQLO_LOCK |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20806852) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 545286226 20806852 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zlaMainThread
zlaProcessMessage
zlaProcessMQIRequest
zlaMQPUT
zsqMQPUT
kpiMQPUT
kqiPutIt
kqiPutMsgSegments
apiPutMessage
aqmPutMessage
aqhPutMessage
aqqWriteMsg
aqlLogPut
almLogIt
hlgWriteLogRecord
xcsFFST

And another unexpected os error:

WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon November 22 22:45:38 GMT Standard Time 2004 |
| Host Name :- UKFAWL02 (Windows 2000 Build 2195: Service Pack 4) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- HL006003 |
| Application Name :- MQM |
| Component :- hlgWriteLogRecord |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- UKMQserv |
| Process Name :- F:\IBM\WebSphere MQ\bin\amqzlaa0.exe |
| Process :- 00003668 |
| Thread :- 00000003 |
| QueueManager :- UKFAWS1P02 |
| Major Errorcode :- hrcE_MQLO_UNEXPECTED_OS_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
zlaMainThread
zlaProcessMessage
zlaProcessMQIRequest
zlaMQOPEN
zsqMQOPEN
kpiMQOPEN
kqiOpenIt
kqiOpenQueue
apiLoadQueue
aqmLoadQueue
aqhLoadQueue
aqqResetQDepth
aqlLogQDepth
almLogIt
hlgWriteLogRecord
xcsFFST
Any help that you can give will be gratefully received. As I say, we've only had this once, but you can guarantee that if we don't follow it up, it will recur somewhere else.

Gilly

JasonE

Posted: Tue Nov 30, 2004 2:09 am Post subject:

Grand Master

Joined: 03 Nov 2003
Posts: 1220
Location: Hursley

Nothing obvious - The fdc you posted was the first one, and the others look slike symptoms (The logger failed for some reason, then the agents fail to write log records, then the checkpointer fails to write log records and probably dies, and finally the execution controller finds the checkpointer process has died).

I cant see, however, what could have caused the original problem - sorry!

Gilly

Posted: Tue Nov 30, 2004 3:28 am Post subject:

Novice

Joined: 27 Jul 2004
Posts: 10
Location: UK

Jason
Thank you for taking the trouble to look into it. Unfortunately, I've not spotted anything else in the system to account for it.
Gilly

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Probe ID: XY035010 (AMQ6125) ; xecL_E_NOT_OWNER

Jump to:

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

Protected by Anti-Spam ACP