+

Search Tips   |   Advanced Search

 

Troubleshoot WebSphere messaging

 

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

 

Overview

To identify and resolve problems that you think are related to WebSphere Messaging, you can use the standard WAS 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 WebSphere MQ as the JMS provider.

 

Procedure

  1. Check for error messages about messaging. For example, check for error messages that indicate a problem with JMS resources.

    Check in the appserver's SystemOut log at was_home\logs\server\SystemOut.

    The associated message reference information provides an explanation and any user actions to resolve the problem.

  2. Check for more informational and error messages that might provide a clue to a related problem. For example, if you have problems accessing JMS resources, check for more error messages and extra details about any problem associated with the JMS provider or with the service integration technologies that the default messaging provider uses.

    For messages related to the resource adapter (JMS) of the default messaging provider, look for the prefix: CWSJR. For messages related to service integration technologies, see the related reference topics.

    If your message-driven bean uses WebSphere Application Server V5 JMS resources, look for the prefixes: MSGS and WMSG.

  3. If you suspect that problems might be related to application use of message-driven beans, see Troubleshooting message-driven beans.

  4. Check the Release Notes for specific problems and workarounds The section Possible Problems and Suggested Fixes of the Release Notes, available from the WAS 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 WAS web site.

  5. Check your JMS resource configurations If the messaging services seem to be running properly, check that the JMS resources have been configured correctly. For example, check that the JMS activation specification against which a message-driven bean is deployed has been configured correctly. For more information about configuring JMS resources, see Use messaging.

  6. Get a detailed exception dump for 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.


WebSphere MQ messaging troubleshooting tips

Troubleshooting message-driven beans

 

Related tasks


Use asynchronous messagingTroubleshooting service integration technologies