"MSGS0101E: Start Queue Manager command failed with exit code: 16" when trying to start the embedded JMS Server in WebSphere Application Server 5.0
 Technote (troubleshooting)
 
Problem(Abstract)
In WebSphere Application Server 5.0 Base, the following exception may occur when the embedded JMS Server starts:

JMSService E MSGS0001E: Starting the JMS Server failed with
exception: java.lang.Exception: MSGS0101E: Start Queue Manager command
failed with exit code: 16

In the createmq.log, several exceptions such as the following are seen:

Exception:java.io.IOException: crtmqm: not found
 
Cause
This problem is most likely to occur on a Unix system when WebSphere Application Server is started by a non-root user. In this case, the non-root user has the necessary permissions to access the WebSphere installation directory, but not the directories under which the embedded MQ queue manager and broker are installed.
 
Resolving the problem
The solution is to give permission to the non-root user to access the MQ installation directories. These directories are:

On Windows NT/2000:
Queue Manager: x:\Program Files\IBM\WebSphere MQ
Broker: x:\Program Files\IBM\WebSphere MQ\WEMPS

On AIX:
Queue Manager: /usr/mqm
Broker: /usr/opt/wemps

On Solaris:
Queue Manager: /var/mqm
Broker: /var/wemps

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1110884
IBM Group: Software Group
Modified date: May 27, 2003