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. |