Messaging errors

 

These hints include a description of the scenario where a problem occurred, the probably reason for the problem and the recommended solution. What kind of problem are you seeing?

• javax.jms.JMSException: MQJMS2008: failed to open MQ queue in JVM log.

• SVC: jms.BrokerCommandFailedExceptfailed: 3008.

If you do not see a problem that resembles yours, or if the information provided does not solve your problem, see Messaging component troubleshooting tips.

If you see WebSphere MQ error messages or reason codes in WebSphere Application Server messages and logs, refer to the WebSphere MQ Messages document at http://publibfi.boulder.ibm.com/epubs/pdf/amqzao05.pdf.

If you are still unable to resolve the problem, see Troubleshooting help from IBM.

 

javax.jms.JMSException: MQJMS2008: failed to open MQ queue in JVM log

This error can occur when the MQ queue name is not defined in the internal JMS server queue names list. This problem can occur if a WAS queue destination is created, without adding the queue name to the internal JMS server queue names list. To resolve this problem:

1. Open the console.

2. Click Servers > Manage Application Servers > server> Server Components > JMS Servers.

3. Add the queue name to the list.

4. Save the changes and restart the server.

 

javax.jms.JMSException: MQJMS3024: unable to start MDB listener

This error can occur if an uninitialized client ID is used (a ClientID that is not associated with a durable subscription). To resolve this problem, set the ClientID in one of the following three ways:

• As a property of the tcf via jmsadmin (for example alter tcf(myTCF) clientid(myID))

• Programmatically using TopicConnection.setClientID()

• Set the Client ID field on the WebSphere MQ topic connection factory resource (for more information, see the related links in this topic).

 

SVC: jms.BrokerCommandFailedExceptfailed: 3008

One possible cause for this error is that you logged on to a Windows 2000 system as an administrator.

To correct this problem, log out and log in again as a user, rather than an administrator.

For current information available from IBM Support on known problems and their resolution, see the IBM Support page.

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.

---

 

Related concepts

Troubleshoot_and_support3240.html

 

Related tasks

WebSphere MQ topic connection factory settings

 

Related Reference

Application deployment troubleshooting tips

 

Reference topic