WebSphere Application Server Connection Manager
Cumulative Fix
Downloadable files
Abstract
This is a Connection Manager cumulative fix for WebSphere®
Application Server 5.0.1/5.0.2
Download Description
This is a cumulative Connection Manager fix, correcting the following
problems
Apars included:
PQ67801 Creation of Oracle DataSources no longer require userid and
password.
Note: Be sure to specify them if you want to call getConnection() with no
parameters, or you want XA recovery to work.
PQ68977 Creation of property to allow logging of orphaned connections.
The property name is 'logOrphan', and can be set via the admin console.
Valid values are 'true' and the default of 'false'. Orphaning is the
process whereby a connection is returned to the pool after a period of
time defined by the orphanTimeout parameter. If the application is working
properly, Orphaning should not occur. Orphaning is typically indicative of
the application holding open connections too long, or caching connections.
PQ69520 Infrastructure support to allow vendor specific calls.
PQ69737 A possible JVM deadlock exists between the transaction timeout
thread and the application processing thread, causing the application to
hang. A workaround is to increase the transaction timeout so in process
transactions do not timeout. This fix resolves the deadlock issue.
PQ70014 License Verification Errors may appear in the Windows Event Viewer
when using the Sequelink or ConnectJDBC drivers. The application/admin
server does not get exceptions, and continues to function normally. This
fix stops the error message from appearing in the Windows Event Viewer.
PQ72349 When looking up a 4.0 style DataSource object from a standalone
Java client, a
(161393) NullPointerException was thrown because the DataSource attempts
to register an MBean with the MBean Server of the process where the lookup
was made from. Clients have no MBean server, resulting in a
NullPointerException. The code was modified to check to see if the MBean
server exists before attempting to register the MBean. If the proces does
not have an MBean server in it, MBean features such as PMI will be
unavailable, but the DataSource will continue to function.
PQ72384 Fix for XA call to getMetaData
PQ72386 Cleanup following a StaleConnectionException may have resulted in
SQLException.
PQ72406 Because of a timing issue, it was possible for a connection which
had been recently retrieved from the connection pool, but not yet used, to
be collected by the orphan timer. This causes a StaleConnectionException
when the application tries to use the connection.
PQ73231 A classloader issue was fixed for users configuring DataSources
using multiple JDBC Provider classes.
PQ73769 A condition existed where on an exception path, PMI data was not
being sent properly the result would be that in Resource Analyzer, the
customer may see more connections in use than they have set as their
maximum.
PQ74478 There was a problem with CMP 1.1 custom finders when running
against DB2/390 where
(112604.3) Access Intent was not being honored appropriately. By applying
this fix and PQXXXXX for the EJB container, the problem will be resolved.
Internal defects included:
119273 and
119273.1 Fix for Oracle exception that is caused by Oracle tight coupling
transaction branches. On oracle 9i the exception is: XAER_RMERR resource
error -3. On oracle 8i the exception is: ="Io exception: End of TNS data
channel", SQLState=null, vendorCode=17002).
This fix requires at minimum (Oracle 9202 or oracle 8174) + Oracle patch
2511780. You will need to set the custom property
(transactionBranchesLooselyCoupled) to true on the datasource.
162498 The message CONM_6021W was appearing to ooften in the logs, it was
changed to show up only once, on pool construction.
162483.4 XARecovery without password exposure. We added a new property,
secureXACredential. This property renders the userid and password
specified on the datasource good for XARecovery -only-. If the
secureXACredential boolean is set to true, the default user and password
properties will not be stored in the referencable, and will only be used
for XA recovery. If the database requires a user and password at runtime,
the application will be required to pass this information on the
getConnection request. CMP beans will require that the user and password
properties be set on the DataSource tab. This provides a configuration
option which is secure, and still allows XA recovery to function. If the
secureXACredential property is not set, or is set to false, the CM
functions as before this fix.
Prerequisites
Please download the UpdateInstaller below to install this fix.