|
Problem(Abstract) |
In WebSphere Application Server V5 the following error may
occur during the attempted startup of the embedded JMS queue manager when
an application server (or a jmsserver in Network Deployment) is starting
on UNIX (AIX, Solaris, HP-UX) or Linux platforms:
MSGS0101E: Start Queue Manager command failed with exit code: 71
This would be seen in the SystemOut.log immediately after this line:
MSGS0050I: Starting the Queue Manager |
|
|
|
Cause |
The MSGS0101E error could occur due to a variety of
causes. The solution described in this document is applicable only if the
exit code is 71 and a file with an .FDC extension is created in the
/var/mqm/errors directory at the same time that the error occurs. Output
similar to the following would be seen in the .FDC file:
| WebSphere MQ First Failure Symptom Report
|
| =========================================
|
| Date/Time :- Tuesday June 14 19:49:09 EST 2005
|
| Host Name :- myhost (HP-UX B.11.11)
|
| PIDS :- 5724B4102
|
| LVLS :- 530.3 CSD03
|
| Product Long Name :- WebSphere MQ for HP-UX
|
| Vendor :- IBM
|
| Probe Id :- XC027049
|
| Application Name :- MQM
|
| Component :- xcsRequestMutexSem
|
| Build Date :- Mar 3 2003
|
| CMVC level :- p530-CSD03J
|
| Build Type :- IKAP - (Production)
|
| UserID :- 00000138 (wsadmin)
|
| Program Name :- endmqcsv_nd
|
| Process :- 00017596
|
| Thread :- 00000001
|
| QueueManager :- WAS_mynode_jmsserver
|
| 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
This output shows that the embedded queue manager cannot access a
semaphore or shared memory segment when it starts up because another MQ
process is already holding it.
Other types of problems that cause MSGS0101E errors are described in this
technote:
Java_Message_Service__JMS_/swg21174832.html |
|
|
Resolving the
problem |
There are two ways to resolve this problem:
The amqiclen command is documented in this technote:
http://www.ibm.com/support/docview.wss?uid=swg21195096
After following these steps, the startup of the embedded queue manager
should be successful. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|