|
Problem |
In the following scenario, WebSphere® Application Server
V4.0.2 is throwing a NullPointerException from a database connection
acquired from a datasource |
|
Cause |
An application runs the following sequence:
The currentBitSet is null because the
CachedStatement.destroy() method is being called before the
CachedStatement.close() method. This is why the currentBitSet =
null, causing the NullPointer exception in the subsequent call to
.close(). |
|
Solution |
APAR PQ60281
fixed the problem by:
- adding the null check for currentBitSet
- ensuring that destroy() didn't get called before
close()
This APAR is included in the latest Connection Manager Cumulative
iFix |
|