MustGather: Connection pooling problems for WebSphere Application Server

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.

Collecting data using IBM Support Assistant

    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.


  1. Using the ISA Data Collector:
    • To run ISADC from command line, go to your app_server_root/bin directory and run isadc.[sh|bat]

      • To download, install and run ISADC locally:
      • Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server.
      • 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.

  2. Select the WebSphere Application Server > Connectors > Database Connection Pooling Problem collector and click Start.

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

Collecting data manually

  1. What is the exact version and edition of the WebSphere Application Server installed?

    For example:
    Base
    Enterprise
    WebSphere Business Integration Server Foundation
    Network Deployment

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

  3. If you are connecting to a database, what is the name and version of the JDBC™ driver that you are using?

  4. If you are connecting to a database, are you using a standard (V5) data source or a V4 data source?

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

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

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

  8. What are the names and JNDI names of the data sources or connection factories that are involved in the problem scenario?

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

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

      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:

        If connecting to a database:

        *=info:WAS.j2c=all:RRA=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.

  11. If the problem takes time to reproduce, enable trace using the procedure under "Dynamic trace" in the document Setting up a trace in WebSphere Application Server which does not require a restart of the application server.

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

  13. Follow instructions to send diagnostic information to IBM support.

  14. For a listing of all technotes, downloads, and educational materials specific to connection pooling, 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 Runtimes for Java Technology Java SDK
Application Servers WebSphere Application Server - Express Java SDK AIX, HP-UX, Linux, Solaris, Windows 8.5, 8.0, 7.0, 6.1, 6.0, 5.1

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
DB Connections/Connection Pooling

Software version:

6.0, 6.1, 7.0, 8.0, 8.5

Operating system(s):

AIX, HP-UX, IBM i, Linux, Solaris, Windows, i5/OS

Software edition:

Base, Express, Network Deployment, WebSphere Business Integration Server Foundation

Reference #:

1254645

Modified date:

2009-11-23

Translate my page

Machine Translation

Content navigation