Use this overview task to help resolve a problem that you
think is related to JMS messaging in WebSphere® Application
Server.
About this task
Note: This topic references one or more of the application
server log files. As a recommended alternative, you 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. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your 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,
you 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.