APAR status |
Closed as program error.
| Error description
System hanging due to NullPointerException when using Websphere
2.0 Connection Manager in Websphere 3.5.3. This happens when a
connection is released back to the pool. Error stack trace is
as follows:
ServletInstan X Uncaught service() exception root cause {0}: {1}
"jsp10"
java.lang.NullPointerException
at com.ibm.ejs.dbm.util.Queue.remove(Queue.java:228)
at com.ibm.ejs.dbm.jdbcext.ConnectionPool.ReturnConnectionToFree
(ConnectionPool.java:1728)
at com.ibm.ejs.dbm.was20.WAS20ConnPool.releaseConnectionObject(W
ConnPool.java:94)
at com.ibm.ejs.dbm.was20.WAS20Connector.releaseConnectionObject(
Connector.java:100)
at com.ibm.servlet.connmgr.IBMConnMgr.releaseIBMConnection(IBMCo
java:115)
at com.ibm.servlet.connmgr.IBMConnection.releaseIBMConnection(IB
ection.java:116)
at com.ibm.ls.igc.servlets.CommonContentBean.getContent(CommonCo
Bean.java:156)
This error will only occur when a WAS 3.5.x user is using the
2.0 Connection Manager API. Must have PQ55402 for this fix.
.
KEYWORDS: WAS Websphere 203 2.03 2.0.3 353 350 3.5 3.5.3 3.5.x as follows:ServletInstan X Uncaught service() exception root cause {0}: {1}"jsp10"java.lang.NullPointerExceptionat com.ibm.ejs.dbm.util.Queue.remove(Queue.java:228)at com.ibm.ejs.dbm.jdbcext.ConnectionPool.ReturnConnectionToFree(ConnectionPool.java:1728)at com.ibm.ejs.dbm.was20.WAS20ConnPool.releaseConnectionObject(WConnPool.java:94)at com.ibm.ejs.dbm.was20.WAS20Connector.releaseConnectionObject(Connector.java:100)at com.ibm.servlet.connmgr.IBMConnMgr.releaseIBMConnection(IBMCojava:115)at com.ibm.servlet.connmgr.IBMConnection.releaseIBMConnection(IBection.java:116)at com.ibm.ls.igc.servlets.CommonContentBean.getContent(CommonCoBean.java:156)This error will only occur when a WAS 3.5.x user is using the, 2.0 Connection Manager API. Must havePQ55402, for this fix..KEYWORDS: WAS Websphere 203 2.03 2.0.3 353 350 3.5 3.5.3 3.5.x Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of the *
* 2.0 ConnMgr API from WebSphere 2.0 *
****************************************************************
* PROBLEM DESCRIPTION: NullPointer exceptions may be *
* received when getting a connection. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Applications that use the WebSphere 2.0 IBMConnMgr
interfaces to get and release connections from the same
connection pool and the gets and release may occur
in overlapping requests, i.e. a get is occurring while
a release is occurring, may receive NullPointer exceptions. Problem conclusion
The WAS20 Connection wrappers were bypassing some of
the synchronization in the 3.5 dbm code and had synchronization
added to the wrappers to try to enforce synchronization in the
wrapper layer but this was not quite correct. The releases
were being synchronized and the removes were synchronized
(sort of) but the gets were not synchronized at all nor was
interaction between the gets, releases and removes synchronized
at all. Synchronization was added to WAS20Connector in order
to make sure all requests were being synchronized. Temporary fixComments
APAR information | APAR number | PQ56607 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-01-11 | Closed date | 2002-01-22 | Last modified date | 2002-01-22 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|