PK71824: WRONG SCHEMA USED

Fixes are available

APAR status

Closed as program error.

Error description

It appears that when a ManagedConnection has its schema
updated per the extended properties mechanism, then it
never gets that schema "put back to normal", even when it is
reused for non-extended connection request.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0 of the heterogeneous pooling feature   *
*                  for data sources                            *
****************************************************************
* PROBLEM DESCRIPTION: Heterogeneous pooling extended          *
*                      properties are not properly reset to    *
*                      their default values.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The error occurs when different sets of heterogeneous pooling
extended properties are configured for the same data source.
For example, one resource reference has (currentSchema=user2,
deferPrepares=false) and another resource reference has
(deferPrepares=true) and another resource reference does not
have any heterogeneous pooling extended properties.  When a
connection is first requested with one set of heterogeneous
pooling extended properties, the values configured in this first
set of heterogeneous pooling extended properties are not cleared
and reset to their default values.  If the connection is pooled
and reused for a second request with a different set of
heterogeneous pooling extended properties or without any
heterogeneous pooling extended properties, then the connection
will have incorrect values for all of the properties that are
not overwritten by this second set of heterogeneous pooling
extended properties.  In our example, after the connection with
the first resource reference is pooled, it is reused with the
second resource reference. The property deferPrepares is
correctly overwriten with a value of true, but the property
currentSchema remains user2 and is not reset to its default
value.  The application receives a connection with an incorrect
currentSchema value.  When the connection is pooled and reused
again for the third resource reference without any heterogeneous
pooling extended properties, the connection has a value of true
for deferPrepares and still has an incorrect value of user2 for
currentSchema

Problem conclusion

Changes were made to take advantage of a new API provided in
version 4 fixpack 3 of the DB2 Universal JCC Driver.
Combined with the JDBC driver fixpack level, changes added
under this APAR allow the application server to keep track of
default values for heterogeneous pooling extended properties
and reset them appropriately.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.1.  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
PK71824
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-11-03
Last modified date
2008-11-03

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
23 October 2021

Tips

PK71824: WRONG SCHEMA USED

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

R700 PSY

Document Information

Share your feedback

Need support?