MSGS0252E: The Broker has terminated unexpectedly
 Technote (troubleshooting)
 
Problem(Abstract)
With IBM® WebSphere® Application Server V5, it is possible that after uninstalling or reinstalling a fix pack, the WebSphere Embedded Messaging broker will fail to start.

The following entries may appear in the SystemOut.log of the application server or the jmsserver (if running WebSphere Application Server Network Deployment):

MSGS0050I: Starting the Queue Manager
MSGS0051I: Queue Manager open for business
MSGS0052I: Starting the Broker
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
at com.ibm.ws.messaging.BrokerManager.pingDFE(BrokerManager.java:344)
at com.ibm.ws.messaging.BrokerManager.startFlows(BrokerManager.java:808)
at com.ibm.ws.messaging.BrokerManager.startBroker(BrokerManager.java:251)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:194)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:289)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
...
 
Cause
One possible cause of the problem is that the MQ_INSTALL_ROOT, MQJMS_LIB_ROOT, and WAS_PUBSUB_ROOT WebSphere environment variables are not set correctly.

You can set the values of these variables in the Administrative Console. To do this, expand Environment and select Manage WebSphere Variables.

The variables should be set as follows:

Variable Name
Value
MQ_INSTALL_ROOT Directory where Embedded Messaging is installed.
The defaults are:
Windows®: C:\Program Files\IBM\WebSphere MQ
AIX®: /usr/mqm
Linux®, Solaris, HP-UX: /opt/mqm
MQJMS_LIB_ROOT ${MQ_INSTALL_ROOT}/java/lib
WAS_PUBSUB_ROOT ${MQ_INSTALL_ROOT}/wemps

The problem could also occur if the bipbroker.jar file, in the ${MQ_INSTALL_ROOT}/wemps/classes directory, is corrupted. This can be tested in a UNIX® environment by using the jar -tvf command to check that the bipbroker.jar contains the com.ibm.broker.server.DataFlowEngine class.

If it does not contain the class, the jar file is corrupted.

 
Resolving the problem
Set the WebSphere environment variables as shown above and ensure that the bipbroker.jar is not corrupted.
If it is corrupted, you can copy the bipbroker.jar from another installation of the same version of WebSphere Application Server and replace the corrupted jar file.
 
 
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.10
Software edition:
Reference #: 1240349
IBM Group: Software Group
Modified date: Jun 28, 2006