|
Problem(Abstract) |
MustGather for 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.0, 5.1 and messaging that does not involve service
integration technologies in V6.0 and V6.1. For problems involving service
integration technologies, refer to MustGather:
Service Integration Technology. |
|
|
|
Resolving the
problem |
 |
You can automatically collect this data using IBM Support
Assistant (ISA) Lite - a special offering that contains the data
collector component of the IBM Support Assistant Workbench.
For a full range of problem-solving features, install the IBM Support Assistant
Workbench - your support workbench for finding answers and solving
problems. The workbench contains all the data collection capability of ISA
Lite plus much more!
|
|
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
JMS specific MustGather information
- 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?
- What messaging system is your application connecting to (WebSphere
Embedded Messaging, WebSphere MQ, or a Generic JMS Provider)?
- 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)?
- 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?
- 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.
|
- 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.
- 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.
- 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 |
|
- 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?
- Send the SystemOut.log file for the application server or
jmsserver on which the problem occurs:
- For WebSphere Application Server V6, 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 |
|
- 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.
|
 |
- Enable a WebSphere Application Server trace.
- Using ISA Lite
a. Start ISA Lite
b. Select Connectors > JMS Problem
c. Follow the prompts to gather the trace and information about your
problem
- For WebSphere Application Server V6:
-
- 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.
- Enter the following trace string:
*=info:Messaging=all:JMSApi=all:WAS.j2c=all:EJBContainer=all |
|
Note: The preceding trace specification should be
entered as one line with no breaks or spaces. |
|
- Click OK and save your configuration.
- Restart the application server.
- Reproduce the problem.
- Send the resulting trace output file.
- For WebSphere Application Server V5:
- 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 trace with the following specification is
selected.
- In the Trace Specification field, enter the following:
Messaging=all=enabled:JMSServer=all=enabled:
JMSApi=all=enabled:WAS.j2c=all=enabled:
EJBContainer=all=enabled |
|
Note: The preceding trace specification should be
entered as one line with no breaks or spaces. |
|
- Under Trace Output, select File, and accept the
defaults.
- Click OK and save your configuration.
- Restart the application server.
- Reproduce the problem.
- Send the resulting trace output file.
1. 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.
2. 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.
3. 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. |
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Application Server Enterprise |
|
AIX, HP-UX, Linux, Solaris, Windows |
5.1, 5.0 |
|
Application Servers |
WebSphere Application Server - Express |
|
AIX, HP-UX, Linux, Solaris, Windows |
6.0, 5.1, 5.0 |
|
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 |
|
|
|
|
|
|