Troubleshooting messaging

Use this overview task to help resolve a problem that you think is related to JMS messaging in WebSphere® Application Server.

About this task

To identify and resolve problems that you think are related to messaging, you can use the standard WebSphere Application Server 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 Version 5 default messaging provider or a third-party messaging provider.

Procedure

  1. Check for error messages about messaging:
    1. Check for error messages that indicate a problem with JMS resources.

      Check in the application server 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 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.

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

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

  3. If you are using the default messaging provider, use the following administrative console panels to inspect the configuration of your applications and JMS resources:
  4. Check the technotes Web page at http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP+SSCMGN&dc=DB520+DB560&dtm for specific problems and solutions.
  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 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, you can enable the application server debug trace for the "Messaging" group to provide a detailed exception dump.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 11:50:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-iseries&topic=tmj_prob0
File name: tmj_prob0.html