Fixes are available
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
In WebSphere v8.5.5.x while testing the JDBCTimingThreshold custom property to identify long running queries and transactions in the application, the timing logic repeatedly threw NullPointerExceptions while reporting long running transactions. These NullPointerExceptions then resulted in application issues requiring the JDBCTimingThreshold property to be disabled. SystemOut.log has the following errors: J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection WSRdbManagedConnectionImpl@ 6d2ac971 from resource jdbc/XXXPool. Caught exception: java.lang.NullPointerException at com.ibm.ws.rsadapter.spi.WSJdbcTiming.dumpTiming ThresholdMessage(WSJdbcTiming.java:72) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl. dissociateConnections(WSRdbManagedConnectionImpl.java:1207) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1797) at com.ibm.ejs.j2c.FreePool.returnToFreePool (FreePool.java:540) at com.ibm.ejs.j2c.PoolManager.release (PoolManager.java:2891) at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager (MCWrapper.java:2608) at com.ibm.ejs.j2c.ConnectionEventListener.connection Closed(ConnectionEventListener.java:384) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl. processConnectionClosedEvent(WSRdbManagedConnection Impl.java:1999) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.close Wrapper(WSJdbcConnection.java:980) at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close (WSJdbcObject.java:242) at com.ibm.ws.rsadapter.jdbc.WSJdbcObject.close (WSJdbcObject.java:195)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using a non-transactional * * datasource with custom property * * JDBCTIMINGTHRESHOLD * **************************************************************** * PROBLEM DESCRIPTION: When there is no transaction on the * * thread, a null point exception can * * occur with JDBCTIMINGTHRESHOLD enabled * **************************************************************** * RECOMMENDATION: * **************************************************************** A null point exception java.lang.NullPointerException at com.ibm.ws.rsadapter.spi.WSJdbcTiming.dumpTiming ThresholdMessage(WSJdbcTiming.java:72) in the WSJdbcTiming code can occur when there is no transaction available.
Problem conclusion
The code does not require a trnasaction and now does not gather the information when a transction is not available. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.14 and 9.0.0.7. 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
PI90290
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-15
Closed date
2018-03-07
Last modified date
2018-03-07
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
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022