IBM Support

MustGather: MQ Java Message Service (JMS) problems with WebSphere Application Server

Technote (troubleshooting)


Problem(Abstract)

Collecting data for WebSphere MQ Java™ Message Service (JMS) problems with IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Note: This MustGather document applies only to messaging in WebSphere Application Server V7.0 and higher that involves MQ JMS Provider. For problems involving
service integration technologies, refer to Mustgather:Service Integration Bus.

Resolving the problem

Tab navigation

Collecting data for WebSphere MQ Java™ Message Service (JMS) problems with IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Note:This MustGather document applies only to messaging in WebSphere Application Server V7.0 and higher that involves MQ JMS Provider. For problems involving service integration technologies, refer to Mustgather:Service Integration Bus.

Read first and related MustGathers

Collecting data manually

  1. What is the exact version and the edition (for example: Base, Enterprise or Network Deployment) of WebSphere Application Server that is installed?

  2. If you are using Publish-Subscribe messaging, what broker are you using (for example: WBI Event Broker, WBI Message Broker, WebSphere MQ Pub/Sub Broker)?

  3. IMPORTANT: If you are using WebSphere Application Server (WAS) V7,V8 or V8.5 and are connecting to WebSphere MQ, ensure the WebSphere MQ Resource Adapter on WAS has been updated after installation of a WAS Fix Pack. Here is a link to a document which lists the WAS V7 V8 and V8.5 Fix Pack levels and corresponding WebSphere MQ Resource Adapter version:

    Which version of WebSphere MQ is shipped with WebSphere Application Server?


    Here are links to Information Center articles on maintaining the WebSphere MQ Resource Adapter and how to ensure the latest version is utilized, respectively:

    WebSphere Application Server V8.5
    Maintaining the WebSphere MQ resource adapter
    Ensuring that servers use the latest available WebSphere MQ resource adapter maintenance level

    WebSphere Application Server V8
    Maintaining the WebSphere MQ resource adapter
    Ensuring that servers use the latest available WebSphere MQ resource adapter maintenance level

    WebSphere Application Server V7
    Maintaining the WebSphere MQ resource adapter
    Ensuring that servers use the latest available WebSphere MQ resource adapter maintenance level
  4. Provide a full description of the problem that you have encountered, including the stack traces of any errors or exceptions that are occurring. Provide any logs that contain the errors or exceptions.
  5. Under what circumstances does the problem occur? Does it occur every time a certain task is done or does it occur intermittently? Has this problem always occurred? If not, was a change recently made before the problem started to occur?
  6. Provide the output from the dspmqver -p2 command on the MQ server side.
  7. Provide the output from the dspmq command. This will show the names and status of all queue managers on your system.
  8. What are the names and JNDI names of the JMS connection factories and destinations that are involved in the problem scenario? If a message-driven bean (MDB) is involved in the problem, what is the name of the listener port/Activation Specification and the MDB?

  9. Send the SystemOut.log file for the application server on which the problem occurs. The file is located in the following directory:

    install_root/profiles/profile_name/logs/server_name
  10. Send the WebSphere MQ error logs located in the following directories:

    MQ_install_root/errors
    MQ_install_root/qmgrs/queue_manager_name/errors

    It is recommended that you clear all of these logs, and then reproduce the problem to produce a fresh set of logs to ensure that the data in the logs is from the current problem.

  11. Enable a WebSphere Application Server trace (NOTE: see step 3 to ensure the WebSphere MQ Resource Adapter is updated for WebSphere Application Server v7 ,v8 and v8.5 prior to generating trace data) .

      1. In the Administrative Console, expand Troubleshooting and select Logs and Trace.

      2. In the Logging and Tracing page, select your server and then Diagnostic Trace.

      3. Ensure that Enable Log is selected.

      4. Under Trace Output, select File, and accept the defaults.

      5. Click OK and save your configuration.

      6. Again expand Troubleshooting and select Logs and Trace.

      7. In the Logging and Tracing page, select your server and then Change Log Detail Levels.

      8. Enter the following trace string:

        WebSphere Application Server V8.0 and V8.5:

        *=info:JMSApi=all:Messaging=all:com.ibm.mq.*=all:WAS.j2c=all:Transaction=all

        WebSphere Application Server V7.0:

        *=info:JMSApi=all:JMSServer=all:Messaging=all:JMS_WASTraceAdapter=all:com.ibm.mq.*=all:jmsApi=all:WAS.j2c=all:Transaction=all

        Note: The preceding trace specifications should be entered as one line with no breaks or spaces.

      9. Click OK and save your configuration.

      10. If WebSphere MQ V7 is being used as the JMS Provider, set the following JVM Custom Property (Application Servers > server_name > Process Definition > Java Virtual Machine > Custom Properties):

        com.ibm.msg.client.commonservices.trace.standalone=false

      11. Click OK and save your configuration.

      12. Restart the application server.

      13. Reproduce the problem.

      14. Send the resulting trace output file.


  12. Enable a WebSphere MQ trace concurrently with the WebSphere Application Server trace.

  13. Run the collector tool to produce a JAR file containing your WebSphere Application Server configuration files and other logs that are useful to the WebSphere Application Server support team.
  14. Follow instructions to send diagnostic information to IBM support to send the files mentioned in the preceding steps.


For a listing of all technotes, downloads, and educational materials specific to JMS, search the WebSphere Application Server support site

Related information
Submitting information to IBM support
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server

Exchanging data with IBM Support

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:


Related information

Recording your screen to share with IBM Support

Cross reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express Java development AIX, HP-UX, Linux, Solaris, Windows 8.5.5, 8.5, 7.0
Application Servers Runtimes for Java Technology Java SDK

Document information

More support for: WebSphere Application Server
Java Message Service (JMS)

Software version: 7.0, 8.0, 8.5, 8.5.5, 9.0

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: Base, Network Deployment

Reference #: 1153217

Modified date: 01 May 2012