Troubleshoot messaging
Use this overview task to help resolve a problem related to JMS messaging in WebSphere Application Server.
IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .
To identify and resolve problems that you think are related to messaging, we can use the standard WAS troubleshooting facilities. Some problems are specific to a particular messaging provider; that is the default messaging provider (service integration), the IBM MQ messaging provider, or a third-party messaging provider.
Tasks
- Check for error messages about messaging:
- Check for error messages that indicate a problem with JMS resources.
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.
- Check for other 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 we suspect that problems might be related to use of message-driven beans, see Troubleshoot message-driven beans.
- If we are using the default messaging provider, use the following administrative console panels to inspect the configuration of the applications and JMS resources:
- For a view of the JMS resources for a given application see: Application messaging resources.
- For a view of the applications and JMS resources for a given default messaging provider destination see: Application resources for this destination.
- Go to the WAS support page to search for information about specific problems and solutions.
- Check your JMS resource configurations.
If the messaging services seem to be running properly, check that the JMS resources have been configured correctly. For information about configuring JMS resources for each of the available messaging providers, see the following topics:
- Configure resources for the default messaging provider
- Configure JMS resources for the IBM messaging provider
- Manage messaging with a third-party JCA 1.5 or 1.6-compliant messaging provider
- Configure JMS resources for a third-party non-JCA messaging provider
- 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.
Subtopics
- Messaging troubleshooting tips
These tips are to help you troubleshoot the WebSphere messaging configuration.- Troubleshoot message-driven beans
Use this overview task to help resolve a problem related to message-driven beans.- Specify write access to the temporary directory to support message-driven bean deployment on listener ports
When deploying a message-driven bean (MDB) against a listener port, we might receive an exception error if the application server's user ID does not have write access to the operating system's temporary directory.- Troubleshoot performance monitoring statistics
Use this task to resolve inconsistencies between performance monitoring statistics for the enterprise bean counters MethodLevelCallCount and MessageCount when deploying message driven beans in a cluster environment.
Maintaining the IBM MQ resource adapter Troubleshoot service integration technologies Use High Performance Extensible Logging to troubleshoot applications Specify write access to the temporary directory to support message-driven bean deployment on listener ports Application messaging resources Application resources for this destination