MQSeries.net :: View topic - Major Errorcode :- xecL_W_SEM_OWNER_DIED

kats

We've MQ 6.0 running on Windows 2003 server SP1. I am having difficulty to start qmgr with amqmdain command. A qmgr got created with crtqmqm and doesn't start with 'amqmdain start qmgrName' command. We are using amqmdain as it starts qmngr under MUSR_MQADMIN. More info on amqmdain : http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/zamqmdain.htm

Well, on fresh install/ of MQ 6.0, I created two qmgr (one with the name XYZ, same as machine name). Initially they worked without any problem. On next day with dspmq command, qmgr XYZ has ended preemptive while other qmgr is still in running mode. When I tried to restart qmgr XYZ, it returns with an error code AMQ7019: An error occurred while creating the directory structure for the new queue manager . So I rebooted the system. On rebooting machine , the 2nd qmgr also got shutdown (the only qmgr that was running before). I tried creating third qmgr on second day but that didn't start at all showing same error code AMQ7019. Since then All of them behaving similarly when given command 'amqmdain start qmgrName'. Though they start normally with strmqm command and can create mq objects under runmqsc console.

I recorded three FDC and couldnâ€™t make out anything of them:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon April 17 14:57:14 Pacific Daylight Time 2006 |
| Host Name :- P259997 (Windows Ver 5.2 Build 3790: Service Pack 1) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.0.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX005035 |
| Application Name :- MQM |
| Component :- zxcProcessChildren |
| SCCS Info :- cmd/zmain/amqzxmb0.c, 1.377 |
| Line Number :- 6033 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Process :- 00000572 |
| Thread :- 00000001 |
| QueueManager :- P259997 |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Major Errorcode :- zrcX_AGENT_DEAD |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ5009 |
| Probe Severity :- 2 |
| Probe Description :- AMQ5009: WebSphere MQ agent process 1572 has |
| terminated unexpectedly. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1572 624 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
ExecCtrlrMain
zxcProcessChildren
xcsFFST
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon April 17 14:57:09 Pacific Daylight Time 2006 |
| Host Name :- P259997 (Windows Ver 5.2 Build 3790: Service Pack 1) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.0.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX092016 |
| Application Name :- MQM |
| Component :- zmuStatisticsCollector |
| SCCS Info :- cmd/zmain/amqzmus0.c, 1.18 |
| Line Number :- 469 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzmur0.exe |
| Process :- 00003068 |
| Thread :- 00000003 |
| QueueManager :- P259997 |
| ConnId(1) IPCC :- 6 |
| ConnId(2) QM :- 11 |
| Major Errorcode :- MQRC_CONNECTION_BROKEN |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ07D9 |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
| message 7D9. |
| FDCSequenceNumber :- 0 |
|
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon April 17 15:26:52 Pacific Daylight Time 2006 |
| Host Name :- P259997 (Windows Ver 5.2 Build 3790: Service Pack 1) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.0.0 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- AT030050 |
| Application Name :- MQM |
| Component :- atmLockDataMutex |
| SCCS Info :- lib/lqm/amqatmua.c, 1.90 |
| Line Number :- 1593 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzmuc0.exe |
| Process :- 00003116 |
| Thread :- 00000003 |
| QueueManager :- P259997 |
| ConnId(2) QM :- 6 |
| Major Errorcode :- xecL_W_SEM_OWNER_DIED |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 3 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+

Mainly, I am having problem with qmgr with same name as machine name. Same name qmgr as machine name behaved weirdly on MQ5.3 and that's a reason we shifted to V6.0. But with V6.0 the case is almost same, only they work fine initially (on fresh install of MQ 6.0) and goes weird next day.
I am testing on a dummy desktop running â€˜Win 2003 SP1â€™ with my OS CD (not the same as we use to image the server) and everything seems to be perfect. Microsoft and IBM are simply not able to able to diagnose: whose problem is this?
Does anybody have any clue?

Raman