IBM Support

MustGather: Connection pooling problems for WebSphere Application Server

Troubleshooting


Problem

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.

Collecting data manually

  1. 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?
  2. 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.
  3. What are the JNDI names of the data sources or connection factories that are involved in the problem scenario?
  4. 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.

 

Enabling J2C traces on WebSphere Application Server:

If you are getting a connection error while using the test connection functionality, please set up the trace on the JVM where the test connection occurs.  Please refer to the table below to determine the correct JVM:

 

Data source scope

JVM where the test connection operation occurs

Cell

Deployment Manager process

Node

Node agent process (of the relevant node)

Cluster

Node agent for each node that contains a cluster member

Server

Server; if the server is unavailable, the test connection operation is retried in the node agent for the node that contains the application server.

 

If the error is not occurring during the test connection, enable the trace on the server(s) where the error or issue is occurring. 
 

For releases of tWAS V9.0, V8.5, V8, and V7:

a.       In the Application Server Administrative Console, expand Troubleshooting and select Logs and Trace.

b.      In the Logging and Tracing page, select your server and then Diagnostic Trace.

c.       Ensure that Enable Log is selected.

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

e.       Click OK and save your configuration.

f.        Again, expand Troubleshooting and select Logs and Trace.

g.      In the Logging and Tracing page, select your server and then Change Log Detail Levels.

h.      Enter the following trace string:

If connecting to a database:


*=info:WAS.j2c=all:RRA=all:Transaction=all

If connecting to a database and having SSL related errors:

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

i.        Click OK and save your configuration.

j.        Restart the Application Server.

k.      Reproduce the problem.

l.        Send the resulting trace output file(s) along with the application server logs and FFDC files.  Follow instructions to send diagnostic information to IBM support

Note:  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.
You can review the following video that walks you through setting up the connection pooling trace in the Administrative Console. It goes through each step listed above to make sure the connection pooling trace is enabled correctly.

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

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"DB Connections\/Connection Pooling","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5;8.0;7.0","Edition":"Base;Express;Network Deployment","Line of Business":{"code":"LOB36","label":"IBM Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","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":null,"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;8.0;7.0;6.1;6.0;5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 February 2020

UID

swg21254645