PK71821: getConnection results in SQLException indicating connection does not exist, when using trusted connections to DB Server

Fixes are available

APAR status

Closed as program error.

Error description

This is a problem that occurs when using trusted connections.
A trusted connection is one that uses security credentials to
open a connection with the DB Server.
   The problem is that if there is an authentication error when
getting a trusted connection, the error handling when this
occurs does not properly reset the connection pool.  It leaves a
connection wrapper in the connection pool that does not
have a valid trusted connection.  When a subsequent
getConnection call is made for a trusted connection, the
connection (MCWrapper) that is in the WebSphere AppServer J2C
connection pool is selected from the pool (since the connection
manager will try to reuse an existing connection).
   When the AppServer then tries to use this connection, it will
receive an SQLException saying that the connection does not
exist.
.
On DB2, the SQLException that is generated is
The application will receive an exception The ERRORCODE=-4470,
SQLSTATE=08003 -4470 is an error code issued by the DB2 JDBC
Universal driver.
 This means the connection does not exist.
.

Local fix

None; though once the SQLException is returned, the invalid
trusted connection should be then removed from the pool.

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of JDBC  *
*                  Datasources enabled for Trusted Context.    *
****************************************************************
* PROBLEM DESCRIPTION: The SQLException occurs after an        *
*                      application attempts to reuse a         *
*                      trusted connection that previously      *
*                      failed with an authentication error.    *
*                      The JCA Connection Manager does not     *
*                      mark the failed connection as stale,    *
*                      and upon reuse, unexpectedly            *
*                      allocates the stale connection to the   *
*                      application rather than destroying it   *
*                      and allocating a new connection.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The symptom occurs after an application attempts to reuse a
trusted connection that previously failed with an
authentication error. The JCA Connection Manager does not mark
the failed connection as stale, and upon reuse, unexpectedly
allocates the stale connection to the application rather than
destroying it and allocating a new connection.

Problem conclusion

APAR PK71821 modifies the JCA Connection Manager to correctly
manage stale trusted connections.  The APAR applies to
WebSphere Application Server 7.0.0.1 and 6.1.0.23

The fix for this APAR is currently targeted for inclusion in
fixpacks 7.0.0.1 and 6.1.0.23.  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
PK71821
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-09
Closed date
2008-10-31
Last modified date
2008-11-21

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

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":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK71821: getConnection results in SQLException indicating connection does not exist, when using trusted connections to DB Server

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?