|
Problem(Abstract) |
MustGather for connection pooling problems for IBM®
WebSphere® Application Server V6.1, V6.0, V5.1, and V5.0. Gathering this
information before calling IBM support will help familiarize you with the
troubleshooting process and save you time. |
|
|
|
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.
Collecting connection pooling specific information
- What is the exact version and edition of the WebSphere Application
Server installed?
For example:
- Base
- Enterprise
- WebSphere Business Integration Server Foundation
- Network Deployment
- What backend system are you connecting to (database, messaging system,
enterprise information system)? What is the name and version of the
backend system? If the backend system is remote, what platform is it
running on?
- If you are connecting to a database, what is the name and version of
the JDBC™ driver that you are using?
- If you are connecting to a database, are you using a standard (V5)
data source or a V4 data source?
- If you are connecting to a database, does the same problem occur when
you perform the same operation in a Java™ program running outside of
WebSphere Application Server using the same JDBC driver to connect to the
database?
- 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?
- What are the names and JNDI names of the data sources or connection
factories that are involved in the problem scenario?
- Send the SystemOut.log file for the application server on
which the problem occurs:
- For V5, the file is located in the following directory:
install_root/logs/server_name |
|
- For V6, the file is located in the following directory:
install_root/profiles/profile_name/logs/server_name |
|
- If the problem can be reproduced easily, enable a WebSphere
Application Server trace:
Note: If you are using a V4 data source, replace
"WAS.j2c=all=enabled:RRA=all=enabled" with "com.ibm.ejs.cm.*=all=enabled"
in the trace V5 trace instructions, and replace "WAS.j2c=all:RRA=all" with
"com.ibm.ejs.cm.*=all" in the V6 trace instructions below.
- For releases of V6.1 and V6:
- In the Application Server 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:
- If connecting to a database:
*=info:WAS.j2c=all:RRA=all:WAS.database=all:Transaction=all |
|
- If connecting to a messaging system:
*=info:WAS.j2c=all:Messaging=all:JMSApi=all:Transaction=all |
|
- If connecting to an enterprise information system:
*=info:WAS.j2c=all:com.ibm.connector2.*=all:Transaction=all |
|
9. Click OK and save your configuration.
10. Restart the Application Server.
11. Reproduce the problem.
12. Send the resulting trace output file.
- For releases of V5.1 and V5:
- In the Application Server 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:
- If connecting to a database in V5.0:
WAS.j2c=all=enabled:RRA=all=enabled:WAS.database=all=enabled:
com.ibm.ejs.jts.*=all=enabled:com.ibm.ws.LocalTransaction.*=all=enabled |
|
- If connecting to a database in V5.1:
WAS.j2c=all=enabled:RRA=all=enabled:WAS.database=all=enabled:
Transaction=all=enabled |
|
- If connecting to a messaging system in V5.0:
WAS.j2c=all=enabled:Messaging=all=enabled:JMSApi=all=enabled:
com.ibm.ejs.jts.*=all=enabled:com.ibm.ws.LocalTransaction.*=all=enabled |
|
- If connecting to a messaging system in V5.1:
WAS.j2c=all=enabled:Messaging=all=enabled:JMSApi=all=enabled:
Transaction=all=enabled |
|
- If connecting to an enterprise information system in V5.0:
WAS.j2c=all=enabled:com.ibm.connector2.*=all=enabled:
com.ibm.ejs.jts.*=all=enabled:com.ibm.ws.LocalTransaction.*=all=enabled |
|
- If connecting to an enterprise information system in V5.1:
WAS.j2c=all=enabled:com.ibm.connector2.*=all=enabled:Transaction=all=enabled |
Note:
If using V4 data source style, please substitute:
WAS.j2c=all=enabled:RRA=all=enabled
with
com.ibm.ejs.cm.*=all=enabled
from the above trace strings |
- 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.
- 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.
- Follow instructions to send
diagnostic information to IBM support.
- For a listing of all technotes, downloads, and educational materials
specific to connection pooling, search the WebSphere
Application Server support site.
|
|
|
|