Use this overview task to help resolve a problem that you
think is related to message-driven beans.
About this task
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:
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 SYSPRINT or SYSOUT log.
The associated message reference information provides an
explanation and any user actions to resolve the problem.
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 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.
The 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.
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.
Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.
This feature requires Internet access.
Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof.
Last updated: Oct 22, 2010 12:21:29 AM CDT http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=tmb_probd File name: tmb_probd.html