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

Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

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, 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.

      [AIX Solaris HP-UX Linux Windows]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.
  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. Go to the WebSphere Application Server support page to search for information about 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.