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:
- Log into the Administrative Console.
- Expand Servers.
- Click Application Servers (or JMS Servers in WebSphere Network
Deployment).
- Select the Application Server or JMS Server in question.
- Click Server Components.
- Click JMS Servers.
- 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.
|