+

Search Tips   |   Advanced Search

Troubleshooting messaging


Use this overview task to help resolve a problem that you think is related to JMS messaging in WAS.

To identify and resolve problems that you think are related to messaging, we can use the standard WAS troubleshooting facilities. Some problems are specific to a particular messaging provider; that is the default messaging provider (service integration), the WebSphere MQ messaging provider, the V5 default messaging provider or a third-party messaging provider.

 

  1. Check for error messages about messaging:

    1. 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 other informational and error messages that might provide a clue to a related problem. For example, if we 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.

  2. If we suspect that problems might be related to use of message-driven beans, see Troubleshooting message-driven beans.

    If the message-driven bean uses WAS V5 JMS resources, look for the prefixes: MSGS and WMSG.

  3. If using the default messaging provider, use the following admin console panels to inspect the configuration of the applications and JMS resources:

  4. Check the Release Notes for specific problems and work arounds.

    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 the problem. If the Release Notes do not contain any information about the problem, we can also search the Technotes database on the WAS web site.

  5. Check the JMS resource configurations. If the messaging services seem to be running properly, check that the JMS resources have been configured correctly. For information about configuring JMS resources for each of the available messaging providers, see the following topics:

  6. Get a detailed exception dump for messaging.

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


Messaging troubleshooting tips
Troubleshooting message-driven beans
Troubleshooting performance monitoring statistics
Adjusting the WebSphere MQ resource adapter configuration when migrating profiles between maintenance level 7.0.0.0 and later levels

 

Related tasks


Troubleshooting service integration technologies

 

Related


Messaging resources for this application
Application resources for this destination