When a second instance of WebSphere Application Server V5
is installed on a host machine where Embedded Messaging is already
installed, no additional MQ files are installed. The existing Embedded MQ
installation is used. However, during the second and subsequent V5
installations with Embedded Messaging, a new queue manager and broker are
created and configured for the new instance. For each instance, a
createmq.node_server.log is created in the $WAS_HOME/logs
directory. The contents of the log show if the Embedded Messaging
components are configured correctly.
In some cases where multiple V5 instances with Embedded Messaging
coexist on one machine, the Embedded queue manager and broker do not start
when the second and subsequent installation of the Application Servers
start. This can be fixed using one of two simple configuration
changes.
Method 1
- Start the Application Server and log on to the Administrative Console.
- In the Administrative Console, expand Servers, then click on
Application Servers.
- Select the Application Server > Server Components
> JMS Servers.
- Change the Initial State property to Started.
- Save the configuration and restart the Application Server.
The Embedded Messaging components now start.
Method 2
Note: This change can also be made by editing the server.xml
file located in the
$WAS_HOME\config\cells\cellname\nodes\nodename\servers\servername
directory.
Find this entry:
<components
xmi:type="messagingserver:JMSServer"
xmi:id="JMSServer_1" name="Internal JMS Server" description="Internal
WebSphere JMS Server" numThreads="1">
<securityPort port="5567" host="localhost"
xmi:id="Address_3"/>
<stateManagement xmi:id="StateManageable_4"
initialState="STOP"/>
</components>
and change it to:
<components xmi:type="messagingserver:JMSServer"
xmi:id="JMSServer_1" name="Internal JMS Server" description="Internal
WebSphere JMS Server" numThreads="1">
<securityPort port="5567" host="localhost"
xmi:id="Address_3"/>
<stateManagement xmi:id="StateManageable_4" initialState="START"/>
</components>
Change the initialState to START, then restart the Application
Server. The Embedded Messaging components now start. |