MDB application unable to start during application server startup
 Technote (troubleshooting)
 
Problem(Abstract)
Message-driven bean (MDB) application unable to start during application server startup in IBM® WebSphere® Application Server V5 with Embedded Messaging.
 
Cause
Two possible errors could appear in the SystemOut.log:

(1) This exception stack trace may appear in the SystemOut.log of the application server during the startup of a message-driven bean (MDB) application:


J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/myTCF. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue
JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB myTopicListenerMDB , JMSDestination jms/myTopic : javax.jms.JMSException: MQJMS2008: failed to open MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:540)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2546)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
...
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1544)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2528)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
...

The above error occurs when the application server attempts to start an application which contains MDBs. During the MDB startup, the application server starts the listener port associated with that particular MDB. If a connection cannot be made to the queue manager to open the proper destination queue, then this type of error will occur.

(2) A second symptom of this problem is the following which would occur on server startup:

MSGS0052I: Starting the Broker
MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
MSGS0001E: Starting the JMS Server failed with exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085

In both cases, the destination queue which cannot be found is the 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' queue. This queue is used internally by WebSphere Embedded Messaging Publish and Subscribe (WEMPS) broker.

To verify that this is the case, examine the createMQ.<node_name>_jmsserver.log to see if the node is federated, or if the createMQ.<node_name>_server1.log is using a non-federated node. The logs can be found in the <WebSphere Application Server install_root>/logs directory.

In the log, the following entry will appear:

Issuing: wempscreatebroker WAS_HELPNOW63DEMO_jmsserver -i dummy -a dummy -q WAS_HELPNOW63DEMO_jmsserver -n "" -u "" -p "" -b -j
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
BIP8051E: Unable to create MQSeries Queue 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' on Queue Manager 'WAS_HELPNOW63DEMO_jmsserver'.
This command attempts to create an MQSeries Queue but was unable to do so.
Locate and resolve the problem and retry the command.
rc=51

This indicates that an error occurred while creating the WEMPS broker, specifically that the 'SYSTEM.BROKER.EXECUTIONGROUP.REPLY' queue was not created successfully.
 
Resolving the problem
The resolution for this problem is to delete and then recreate the embedded messaging queue manager and broker.

This is done by running the createMQ.[sh|bat] and deleteMQ.[sh|bat] scripts.

(1) Stop all WebSphere Application Server processes (dmgr, nodeagent, appservers, jmsserver)

(2) From the <WebSphere Application Server install_root>/bin directory, invoke the deleteMQ script. The syntax is as follows:


deletemq cell_name node_name server_name

NOTE: In a Network Deployment environment, the 'server_name' is 'jmsserver'

(3) Then, from the same directory, invoke the createMQ script. The syntax is as follows:


createmq was_home cell_name node_name server_name messaging_dir broker_dir

(4) Now, start the WebSphere Application Server processes. The problem should be resolved.

See the following Information Center links for more information on the deleteMQ and createMQ commands:

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rmj_createmq.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rmj_deletemq.html

 
Related information
deleteMQ command
createMQ command
 
 
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.6
Software edition:
Reference #: 1223157
IBM Group: Software Group
Modified date: Nov 18, 2005