PK83902: CONNECTION STACK TRACE INFORMATION FOR LONG-RUNNING CONNECTIONS CANNOT BE OBTAINED WITHOUT ENABLING WAS.J2C TRACING.

Fixes are available

APAR status

Closed as program error.

Error description

When using WebSphere Application Server connection pooling, it
is possible for a customer's application to gradually 'leak'
connections over time.

In one of these types of scenarios, an application component
will get a connection from the WebSphere Application Server's
connection pool, use it, and then not close it.

This behavior occurs at infrequent intervals over the lifetime
of the running JVM.  Eventually, the connection pool for the
datasource being used will max out resulting
ConnectionWaitTimeoutExceptions being thrown back to
applications which need to get a connection.

Debugging this type of problem requires running WAS.j2c=all
traces for a long period of time.  This type of tracing is
performance intensive and has the potential to log a large
amount of data.

The only data which is needed is the stack trace of the
connections which are not closed.  There needs to be a mechanism
by which a non-intrusive trace is enabled to collect the data in
memory so that the showPoolContents command can then output the
data when a long-running connection is identified.

Local fix

```
Use WAS.j2c=all tracing.
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using J2EE Connector Architecture    *
*                  (JCA)                                       *
****************************************************************
* PROBLEM DESCRIPTION: You are not able to see stack           *
*                      information without turning on a        *
*                      WAS.j2c trace when using MBeans to      *
*                      display the connection pool.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The was.j2c trace slowed the system process or made it
difficult to reproduce a long running problem when using
mbeans to display connection pool information.

Problem conclusion

ConnLeakLogic=all now can be used with this apar to enable
stack information to be displayed when using mbeans to display
connection pool information.  This performs much better and
provides the required information without full WAS.j2c trace
enabled.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.37, 6.1.0.27, and 7.0.0.5.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK83902
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-01
Closed date
2009-06-11
Last modified date
2009-06-11

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK83902: CONNECTION STACK TRACE INFORMATION FOR LONG-RUNNING CONNECTIONS CANNOT BE OBTAINED WITHOUT ENABLING WAS.J2C TRACING.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?