Embedded Messaging Broker does not start when the WebSphere® V5 Test Server is started in WebSphere Studio Application Developer
 Technote (troubleshooting)
 
Problem(Abstract)
When starting a WebSphere Application Server V5 Test Server within WebSphere Studio Application Developer V5 releases, the Embedded Publish and Subscribe Broker might not start properly. You might see the following errors in the WebSphere Studio Application Developer Console after the Embedded Queue Manager starts successfully:

MSGS0201E: Unable to start the Broker because WebSphere Embedded Messaging Server support not been installed

MSGS0252E: The Broker has terminated unexpectedly

MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0252E: The Broker has terminated unexpectedly
 
Cause
The most likely cause of this problem is that the WebSphere Test Server configuration is not configured with the location of the WebSphere Embedded Messaging Publish & Subscribe (WEMPS) Broker.
 
Resolving the problem
To correct this problem:
  1. Edit the Server configuration within WebSphere Studio Application Developer.
  2. Select the Variables tab.
  3. Select the WAS_PUBSUB_ROOT environment variable under Node Settings.
  4. Click Edit and type the directory where WEMPS is installed as the value.

    The default WEMPS installation directory is:

    Windows®: C:\Program Files\IBM\WebSphere MQ\WEMPS

    Linux®: /opt/wemps
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Software Development WebSphere Studio Application Developer JMS Linux, Windows 5.0, 5.0.1, 5.1, 5.1.1 All Editions
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 #: 1162746
IBM Group: Software Group
Modified date: Mar 9, 2004