+

Search Tips   |   Advanced Search

Troubleshoot message-driven beans

Use this overview task to help resolve a problem related to message-driven beans.

IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer . essage-driven beans support uses the standard WebSphere Application Server troubleshooting facilities. If we encounter a problem that you think might be related to the message-driven beans.


Tasks

  1. Check for error messages about message-driven beans:

    1. Check for error messages that indicate a problem with JMS resources, such as activation specifications or listener ports, used by message-driven beans.

      Check in the application server SystemOut log at was_home\logs\server\SystemOut.

      (ZOS) Check in the SYSPRINT or SYSOUT log.

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

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

  2. If we are using the default messaging provider, use the following administrative console panels to inspect the configuration of our message-driven beans:

  3. 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 website, is updated regularly to contain information about known defects and their workarounds. Check the latest version of the Release Notes for any information about our problem. If the Release Notes does not contain any information about our problem, we can also search the Technotes database on the WAS website.

  4. If the message-driven bean is deployed against a listener port, check that the listener port has started. The message listener service is an extension to the JMS functions of the JMS provider. For each message-driven bean mapped to a listener port, the message listener service controls a listener that monitors a JMS destination on behalf of a deployed message-driven bean.

  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 the message-driven bean is deployed has been configured correctly.

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


Related:

  • Message-driven beans, activation specifications, and listener ports
  • Manage message listener resources for message-driven beans
  • Use High Performance Extensible Logging to troubleshoot applications
  • (ZOS) Optimizing MDB throttle support for debugging in z/OS
  • Application messaging resources
  • Application resources for this destination