MSGS0252E: The Broker has terminated unexpectedly, MSGS0200E: The Broker DataFlowEngine return code was: 1
 Technote (troubleshooting)
 
Problem(Abstract)
With Global Security enabled:

JMS Broker failed to start with MSGS0200E, MSGS0252E

[5/12/04 9:38:58:600 CDT] 717a73 BrokerDFEThre E MSGS0200E: The Broker
DataFlowEngine return code was: 1
[5/12/04 9:42:01:980 CDT] 13dee9 BrokerManager E MSGS0252E: The Broker
has terminated unexpectedly
[5/12/04 9:42:03:876 CDT] 13dee9 JMSService E 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(JMSEmbeddedProviderIm
pl.java:194)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
 
Cause
This problem can be because the broker is unable to access some semaphores that it needs.

When the JMSServer is installed, the WEMPS broker creates a number of semaphores. The semaphores are owned by root, and remain on the system until either the system is restarted, or the semaphores are deleted by the user.

The WEMPS broker attempts to access these semaphores as part of the startup routine. If the semaphores do not exist, it creates them. However, if the semaphores are created using a different user than the one who is trying to access them, an error occurs and the broker fails to start.

It is suspected that the reason the WEMPS broker fails to start is because the shared memory semaphores are created by a different user than the non-root user that is starting WebSphere Application Server.

If you have not restarted the system since the JMSServer was installed, the semaphores are owned by root, and not the non-root user. Because the semaphores already exist, WEMPS attempts to reuse them, but is unable to because the non-root user does not have permission to access them.

 
Resolving the problem
Restarting the system will solve this problem.
 

Detailed stack from the SystemOut of the JMS Server

[5/12/04 9:38:44:147 CDT] 13dee9 JMSEmbeddedPr A MSGS0051I: Queue
Manager open for business
[5/12/04 9:38:44:168 CDT] 13dee9 JMSEmbeddedPr A MSGS0052I: Starting
the Broker
[5/12/04 9:38:58:600 CDT] 717a73 BrokerDFEThre E MSGS0200E: The Broker
DataFlowEngine return code was: 1
[5/12/04 9:42:01:980 CDT] 13dee9 BrokerManager E MSGS0252E: The Broker
has terminated unexpectedly
[5/12/04 9:42:03:876 CDT] 13dee9 JMSService E 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(JMSEmbeddedProviderIm
pl.java:194)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
..

 
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): Solaris
Software version: 5.0.2.6
Software edition:
Reference #: 1175925
IBM Group: Software Group
Modified date: Aug 3, 2004