Troubleshoot WebSphere Messaging

Use this overview task to help resolve a problem that you think is related to the WebSphere Messaging.

To identify and resolve problems that you think are related to WebSphere Messaging, you can use the standard WebSphere Application Server troubleshooting facilities. If you encounter a problem that you think might be related to WebSphere Messaging, complete the following stages. Some problems and their troubleshooting are specific to whether you are using the embedded WebSphere Messaging or MQ as the JMS provider.

 

  1. Check for common problems related to WebSphere Messaging. For example, check that the JMS server has been started, that you have added queue names to the list on the JMS server page of the Administrative Console, and that you have successfully installed the WebSphere Messaging function.

    For tips about solving problems related to the WebSphere Messaging, see Tips for troubleshooting WebSphere Messaging. If those tips do not help you fix the problem, complete the following general stages.

  2. Check the Release Notes for specific problems and workarounds The section Possible Problems and Suggested Fixes of the Release Notes, available from the WebSphere Application Server library web site, is updated regularly to contain information about known defects and their workarounds. Check the latest version of the Release Notes for any information about your problem. If the Release Notes do not contain any information about your problem, you can also search the Technotes database on the WebSphere Application Server web site.

  3. Check for WebSphere Messaging messages in the appserver's SystemOut log at was_home\logs\server\SystemOut. Check the SystemOut log for error messages for messages related to WebSphere Messaging; look for the prefixes MSGS and WMSG. The associated Message reference information provides an explanation and any user actions to resolve the problem.

  4. Check for more messages in the appserver's SystemOut log. If the JMS server is running, but you have problems accessing JMS resources, check the SystemOut log file, which should contain more error messages and extra details about the problem.

    For messages related to WebSphere Messaging, look for the prefixes: MSGS and WMSG.

  5. Check your JMS resource configurations If the WebSphere Messaging functions seem to be running properly (the JMS server is running without problems), check that the JMS resources have been configured correctly. For example, check that queue destinations and their connection factories have corresponding JNDI names, that the JNDI names match those configured for the messaging applications, and that the connection factories are configured onto nodes that can provide the JMS resources.

  6. (Optional)  

    Get a detailed exception dump for WebSphere Messaging. If the information obtained in the preceding steps is still inconclusive, you can enable the appserver debug trace for the "Messaging" group to provide a detailed exception dump.

Troubleshooting message-driven beans
Administering WebSphere JMS support
Using JMS and messaging in applications
Tips for troubleshooting WebSphere Messaging

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.