Embedded Queue Manager in WebSphere Application Server V5.0 does not start resulting in connection errors in SystemOut.log
 Technote (troubleshooting)
 
Problem(Abstract)
The embedded queue manager and broker in IBM® WebSphere® Application Server V5.0 does not start when the application server (or JMS Server in a federated environment) is started. When an application tries to establish a connection to the queue manager or broker, the following connection errors occur:

J2CA0046E: Method createManagedConnctionWithMCWrapper caught an exception during creation of the ManagedConnection for resource <resource>, throwing ResourceAllocationException. Original exception: javax.resource.spi.ResourceAdapterInternalException: JMSException in createConnection

Caused by:
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
 
Cause
Reason code 2059 indicates that the queue manager is not available. In this case, the startup of the embedded queue manager and broker may be disabled.
 
Resolving the problem
Check to see if the embedded queue manager and broker startup is disabled. You can do this in two ways, but the preferred way is through the Administrative Console:

1) In the Administrative Console:

  1. Log into the Administrative Console.
  2. Expand Servers.
  3. Click Application Servers (or JMS Servers in WebSphere Network Deployment).
  4. Select the Application Server or JMS Server in question.
  5. Click Server Components.
  6. Click JMS Servers.
  7. Check the Initial State. If it is set to Stopped, change it to Started, then save your configuration and restart the application server or JMS Server so that the embedded queue manager and broker will start.

2) In the server.xml file, located in the

<WebSphere install root>/config/cells/cell name/nodes/node name/servers/server name directory. Look for this xml entry:


<components xmi:type="messagingserver:JMSServer" xmi:id="JMSServer_1"
name="Internal JMS Server" description="Internal WebSphere JMS Server"
numThreads="1">
<stateManagement xmi:id="StateManageable_4" initialState="STOP"/>

If the initialState is set to STOP, change it to START, save the change to the xml file, and then start the application server or JMS Server so that the embedded queue manager and broker will start.

3) If the above suggestions do not work, then see the Mustgather for JMS problems to continue investigation.

 
 
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.1.1
Software edition:
Reference #: 1210876
IBM Group: Software Group
Modified date: Jun 30, 2005