PM86076: TESTCONNECTION OPERATION OF A ORACLE UCP DATASOURCE FAILED with ClassNotFoundException

Fixes are available

APAR status

Closed as program error.

Error description

TestConnection operation of a Oracle UCP datasource in a
Network Deployment edition environment fails.

Results in the following exception :
*************************************
java.sql.SQLException: Unable to start the Universal Connection
Pool: oracle.ucp.UniversalConnectionPoolException: Error during
pool creation in Universal Connection Pool Manager MBean:

oracle.ucp.UniversalConnectionPoolException: Error during pool
creation in Universal Connection Pool Manager:
java.sql.SQLException: Invalid

Universal Connection Pool configuration: java.sql.SQLException:
Unable to create factory class instance with provided factory
class  name:
java.lang.ClassNotFoundException:
oracle.jdbc.xa.client.OracleXADataSource DSRA0010E: SQL State =
null, Error Code = 0 at
oracle.ucp.util.UCPErrorHandler.newSQLException(UCPErrorHandler.
java:488 ) at
oracle.ucp.util.UCPErrorHandler.throwSQLException(UCPErrorHandle
r.java:1
*******************************************************

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: TestConnection operation of Oracle      *
*                      UCP Datasource in a Network Deployment  *
*                      environment fails with                  *
*                      ClassNotFoundException                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
With the UCP cluster scoped datasource on a Network Deployment
environment, the testConnection operation can result in a
failure
due to ClassNotFoundException. The reason is that during the
testConnection call the ucp.jar and ojdbc6.jar are loaded
using URLClassloader with the current thread context
classloader as the parent classloader.
However on calling the getConnection(), the driver seems to be
loading the factory class oracle.jdbc.pool.OracleDataSource or
oracle.jdbc.xa.client.OracleXADataSource using the threads
context classloader.
Since the jars were loaded using the URLClassLoader(child of
thread context classloader) and when the
oracle.jdbc.pool.OracleDataSource is attempted to load using
the current thread context classloader(parent) the class is
not visible and hence the ClassNotFoundException.

Problem conclusion

The WebSphere adapter testConnection code has been updated to
handle the class loading appropriately to avoid the
ClassNotFoundException.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31, 8.0.0.8, and 8.5.5.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
PM86076
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-02
Closed date
2013-06-27
Last modified date
2013-06-27

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 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:
11 January 2022

Tips

PM86076: TESTCONNECTION OPERATION OF A ORACLE UCP DATASOURCE FAILED with ClassNotFoundException

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?