Troubleshooting message-driven beans

Use this overview task to help resolve a problem that you think is related to message-driven beans.

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.

Message-driven beans support uses the standard WebSphere® Application Server troubleshooting facilities. If you encounter a problem that you think might be related to the message-driven beans, complete the following steps.

Procedure

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, that are used by message-driven beans.
  
  Check in the application server SystemOut log at was_home\logs\server\SystemOut.
  
  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 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 Version 5 JMS resources, look for the prefixes: MSGS and WMSG.
If you are using the default messaging provider, use the following administrative console panels to inspect the configuration of your message-driven beans:
- For a view of the JMS resources for a given message-driven bean, see the following panel: Messaging resources for this application.
- For a view of the message-driven beans and JMS resources for a given default messaging provider destination, see the following panel: Application resources for this destination.
Check the Release Notes for specific problems and workarounds.
If your 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.
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.
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.