Troubleshoot message-driven beans

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

 

Overview

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 stages:

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

    Check in the appserver's SystemOut log at was_home\logs\server\SystemOut for error messages that indicate a problem with JMS resources for message-driven beans, such as listener ports.

    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.If the JMS server is running, but you have problems accessing JMS resources, check for more error messages and extra details about the problem.

    For messages related to WebSphere Messaging, look for the prefixes: MSGS and WMSG.

  3. Check the Release Notes for specific problems and workaroundsThe section Possible Problems and Suggested Fixes of the Release Notes, available from the WebSphere Application Server 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 your problem. If the Release Notes does not contain any information about your problem, you can also search the Technotes database on the WebSphere Application Server web site.

  4. Check that message listener service has started.The message listener service is an extension to the JMS functions of the JMS provider. It provides a listener manager that controls and monitors one or more JMS listeners, which each monitor a JMS destination on behalf of a deployed message-driven bean.

  5. Check your JMS resource configurationsIf the WebSphere Messaging functions seem to be running properly (the JMS server is running without problems), check that the JMS resources have been configured correctly. For example, check that the listener ports have been configured correctly and have been started.

  6. Check for problems with the WebSphere Messaging functions For more information about troubleshooting WebSphere Messaging, see the related topics.

  7. Get a detailed exception dump for messaging.If the information obtained in the preceding steps is still inconclusive, you can enable the appserver debug trace for the "Messaging" group to provide a detailed exception dump.
Related tasks
Configuring message listener resources for message-driven beans
Developing an enterprise application to use message-driven beans
Using message-driven beans in applications
Troubleshooting WebSphere Messaging