Troubleshooting extended messaging

Use this overview task to help resolve a problem that you think is related to the extended messaging service.

Why and when to perform this task

The extended messaging service uses the standard WebSphere Application Server RAS facilities. If you encounter a problem that you think might be related to the extended messaging service, complete the following stages:

Steps for this task

  1. Check for extended messaging service messages in the application server's SystemOut log at was_home\logs\server_name\SystemOut.
    Any error messages associated with the extended messaging service are labelled with EMSG. The error message indicates the nature of the problem and provides some detail. The extended messaging service issues EMSG error messages if it fails to initialize, parse its configuration file, or encounters some runtime error.
  2. Check for more messages in the application server's SystemOut log.
    If the JMS server is running, but you have problems accessing JMS resources, check the SystemOut log file, which should contain more error messages and extra details about the problem.
  3. 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.
  4. Check for problems with the WebSphere Messaging functions or message-driven beans
    For more information about troubleshooting WebSphere Messaging, see the related topics listed at the bottom of this file.
  5. Get a detailed exception dump for extended 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.

Related tasks
Developing an enterprise application to use extended messaging
Deploying an enterprise application to use extended messaging
Configuring extended messaging service resources
Using extended messaging in applications
Troubleshooting message-driven beans
Troubleshooting WebSphere Messaging
Related reference
Important files for message-driven beans and extended messaging



Searchable topic ID:   tmc_probd
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/cmm/tasks/tmc_probd.html

Library | Support | Terms of Use | Feedback