Troubleshooting
Problem
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
- Learning more
- Troubleshooting
- Collecting data- selected tab,
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.
MustGather: Read first for WebSphere Application Server
For a list of all technotes, downloads, and educational materials, search the WebSphere Application Server support site.
Troubleshooting guide for WebSphere Application Server
Steps to get support for WebSphere Application Server
- What is the exact version and the edition (for example: Base, Enterprise or Network Deployment) of WebSphere Application Server that is installed?
- 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)?
- 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 V9.0
Maintaining the WebSphere MQ resource adapter
Ensuring that servers use the latest available WebSphere MQ resource adapter maintenance level
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
- 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.
- 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?
- Provide the output from the dspmqver -p2 command on the MQ server side.
- Provide the output from the dspmq command. This will show the names and status of all queue managers on your system.
- 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?
- 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
- 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.
- 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) .
- In the Administrative Console, expand Troubleshooting and select Logs and Trace.
- In the Logging and Tracing page, select your server and then Diagnostic Trace.
- Ensure that Enable Log is selected.
- Under Trace Output, select File, and accept the defaults.
- Click OK and save your configuration.
- Again expand Troubleshooting and select Logs and Trace.
- In the Logging and Tracing page, select your server and then Change Log Detail Levels.
- Enable a WebSphere MQ trace concurrently with the WebSphere Application Server trace.
- 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.
- Gathering information with the collector tool-V9.0
- Gathering information with the collector tool - V8.0 and V8.5
- Gathering information with the collector tool - V7.0
- 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
- Enter the following trace string:
WebSphere Application Server V9.0:
*=info:jmsApi=all:Messaging=all:com.ibm.mq.*=all:JMSApi=all:com.ibm.ws.cdi.jms*=all:WAS.j2c=all:Transaction=all
WebSphere Application Server V8.0 and V8.5:
*=info:jmsApi=all:Messaging=all:com.ibm.mq.*=all:JMSApi=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.
Click OK and save your configuration.
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
Click OK and save your configuration.
Restart the application server.
Reproduce the problem.
Send the resulting trace output file.
Steps to getting support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server
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:
- IBM Support Assistant (ISA)
- Service Request (SR)
- FTP to the Enhanced Customer Data Repository (ECuRep)
Related Information
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java Message Service (JMS)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.5;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java development","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.5;8.5;7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]