Technote (troubleshooting)

Problem(Abstract)

Collecting data for connection pooling problems for IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving the problem

Tab navigation

Collecting data for connection pooling problems for IBM WebSphere Application Server. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

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.

Beginning with
WebSphere Application Server V8.0.0.6, the IBM Support Assistant Data Collector
(ISADC) tool is bundled with the product and is automatically installed. As a result, you can run the
ISADC tool directly from the app_server_root/bin directory. Note: ISADC is not bundled with the WebSphere Application Server Liberty Profile. For more details, see
Using the IBM Support Assistant Data Collector.

Using the ISA Data Collector:

To run ISADC from command line, go to your app_server_root/bin directory and run isadc.[sh|bat]

What back-end system are you connecting to (database, messaging system, enterprise information system)? What is the name and version of the back-end system? If the back-end 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:

profile_root/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:RRA=all" with "com.ibm.ejs.cm.*=all" in the trace instructions below.

For releases of V8.5, V8, V7, V6.1 and V6.0:

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. It is recommended to set the number of historical trace files to 10 and the size of each historical trace file to 100MB.

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.

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: