MustGather: Java Message Service (JMS) problems (not involving Service Integration Technologies) 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 WebSphere Application Server V5.1 and messaging that does not involve service integration technologies in V6.0, V6.1, V7.0, V8.0, and V8.5. For problems involving service integration technologies, refer to MustGather: Service Integration Technology.

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 WebSphere Application Server V5.1 and messaging that does not involve service integration technologies in V6.0, V6.1, V7.0 and V8.0. For problems involving service integration technologies, refer to MustGather: Service Integration Technology.

To improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.

Collecting data using the IBM Support Assistant Data Collector

  1. Go to the ISA Data Collector site for WebSphere Application Server.

  2. Start the ISA Data Collector:
    • To run online, select the option to collect from this system using the current browser and click Start Collection.

    • To run locally, select the option to collect from this or another system using a downloadable utility. Download and extract the zip file to your WAS_HOME directory. From a command line, run isadc.[sh|bat] or launch index.html to use the web interface.

    • Beginning with WebSphere Application Server V8.0.0.6, the IBM Support Assistant Data Collector (ISADC) tool is bundled with the product. The ISADC tool is also provided for the WebSphere Application Server Liberty profile starting with V8.5.0.1.  As a result, you can run the ISADC tool directly from the app_server_root/bin directory. For more details, see Using the IBM Support Assistant Data Collector

  3. Select the Connectors > JMS Problem collector and click Start.

  4. Follow the prompts to automatically submit the collected data to IBM Support.

Collecting data manually

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

  2. What messaging system is your application connecting to (WebSphere Embedded Messaging, WebSphere MQ, or a Generic JMS Provider)?

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

  4. IMPORTANT: If you are using WebSphere Application Server (WAS) V7 or V8 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 and V8 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
    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

  5. 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.

  6. 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?

  7. If you are using the WebSphere JMS Provider (Embedded Messaging) or the WebSphere MQ V5.3 JMS Provider, provide the output from the mqver command. Example of the output:

    Name:        WebSphere MQ
    Version:     530.10  CSD10
    CMVC level:  p530-10-L050419
    BuildType:   IKAP - (Production)


    If you are using WebSphere MQ V6.0, provide the output from dspmqver -p2 instead of mqver.

  8. If you are using WebSphere MQ and the MQ server is remote, provide the output from the mqver (for MQ V5.3) or dspmqver -p2 (for MQ V6.0) command on the client side.

  9. If you are using the WebSphere JMS Provider (Embedded Messaging) or the WebSphere MQ JMS Provider, provide the output from the dspmq command. This will show the names and status of all queue managers on your system.

  10. If you are using Embedded Messaging, do the embedded queue manager and broker start successfully? Check for the following lines in the SystemOut.log file of the application server or the jmsserver (if running in a Network Deployment environment):

    MSGS0050I: Starting the Queue Manager
    MSGS0051I: Queue Manager open for business
    MSGS0052I: Starting the Broker
    MSGS0053I: Broker open for business


  11. 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 and the MDB?

  12. Send the SystemOut.log file for the application server or jmsserver on which the problem occurs:
    • For WebSphere Application Server V6, V7, V8, and V8.5, the file is located in the following directory:

      install_root/profiles/profile_name/logs/server_name

    • For WebSphere Application Server V5, the file is located in the following directory:

      install_root/logs/server_name

  13. If you are using the WebSphere JMS Provider (Embedded Messaging) or the WebSphere MQ JMS Provider, 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.

  14. Enable a WebSphere Application Server trace (NOTE: see step 4 to ensure the WebSphere MQ Resource Adapter is updated for WebSphere Application Server v7 and v8 prior to generating trace data) .
    • Using ISA Lite
      1. Start ISA Lite.
      2. Select Connectors > JMS Problem.
      3. Follow the prompts to gather the trace and information about your problem.

    • For WebSphere Application Server V6, V7, V8, and V8.5:
      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 V6 and 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.

    • For WebSphere Application Server V5:
      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 trace with the following specification is selected.

      4. In the Trace Specification field, enter the following:

        Messaging=all=enabled:JMSServer=all=enabled:JMSApi=all=enabled:WAS.j2c=all=enabled:EJBContainer=all=enabled:jmsApi=all=enabled

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

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

      6. Click OK and save your configuration.

      7. Restart the application server.

      8. Reproduce the problem.

      9. Send the resulting trace output file.

  15. If you are using the WebSphere JMS Provider (Embedded Messaging) or the WebSphere MQ JMS Provider, enable a WebSphere MQ trace concurrently with the WebSphere Application Server trace.

  16. 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.
  17. 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:


Read first and related MustGathers

Cross reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express Java development AIX, HP-UX, Linux, Solaris, Windows 7.0, 6.1, 6.0, 5.1
Business Integration WebSphere Business Integration Server Foundation AIX, HP-UX, Linux, Solaris, Windows 5.1, 5.0
Application Servers Runtimes for Java Technology Java SDK

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
Java Message Service (JMS)

Software version:

6.0, 6.1, 7.0, 8.0, 8.5, 8.5.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Base, Network Deployment

Reference #:

1153217

Modified date:

2012-05-01

Translate my page

Machine Translation

Content navigation