Troubleshooting messaging
Use this overview task to help resolve a problem that you think is related to JMS messaging in WebSphere Application Server.
This topic references one or more of the application server log files. As a recommended alternative, we 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. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.
To identify and resolve problems that you think are related to messaging, we can use the standard WebSphere Application Server troubleshooting facilities. Some problems are specific to a particular messaging provider; that is the default messaging provider (service integration), the WebSphere MQ messaging provider, or a third-party messaging provider.
- 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.
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 Troubleshooting message-driven beans.
- For 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 the following panel: Messaging resources for this application.
- For a view of the applications and JMS resources for a given default messaging provider destination, see the following panel: Application resources for this destination.
- Go to the WebSphere Application Server support page to search for information about specific problems and solutions.
- Check the 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 WebSphere MQ 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 troubleshoot the WebSphere messaging configuration.
- Troubleshooting message-driven beans
Use this overview task to help resolve a problem that you think is 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, you might receive an exception error if the application server's user ID does not have write access to the operating system's temporary directory.
- Troubleshooting 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.
Related tasks
Maintain the WebSphere MQ resource adapter Troubleshooting 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
Messaging resources for this application Application resources for this destination