Fixes are available
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
The following NullPointerException can occur on the nodeagent when starting TPVLogging(using wsadmin script) for 2 different servers NodeAgent SystemOut.log -- [2/26/16 10:17:14:879 JST] 0000007b SystemErr R java.lang.NullPointerException [2/26/16 10:17:14:889 JST] 0000007b SystemErr R at com.ibm.ws.performance.tuning.serverAlert.calc.config.ServerRJvm ConfigCalc.getInitialHeapSize(ServerRJvmConfigCalc.java:112) [2/26/16 10:17:14:889 JST] 0000007b SystemErr R at com.ibm.ws.performance.tuning.serverAlert.calc.config.ServerRJvm ConfigCalc.getConfigMap(ServerRJvmConfigCalc.java:197) [2/26/16 10:17:14:889 JST] 0000007b SystemErr R at com.ibm.ws.performance.tuning.calc.AbstractCalcWriter.writeConfi g(AbstractCalcWriter.java:118) [2/26/16 10:17:14:889 JST] 0000007b SystemErr R at com.ibm.ws.tpv.engine.logger.WriteStatLog.<init>(WriteStatLog.ja va:121) [2/26/16 10:17:14:890 JST] 0000007b SystemErr R at com.ibm.ws.tpv.engine.logger.WriteXMLStatLog.<init>(WriteXMLStat Log.java:34) [2/26/16 10:17:14:890 JST] 0000007b SystemErr R at com.ibm.ws.tpv.engine.logger.TPVLoggingImpl.startLogging(TPVLogg ingImpl.java:62) [2/26/16 10:17:14:890 JST] 0000007b SystemErr R at com.ibm.ws.tpv.engine.TPVEngine.startLogging(TPVEngine.java:592) [2/26/16 10:17:14:890 JST] 0000007b SystemErr R at com.ibm.ws.tpv.engine.TPVCollaborator.startLogging(TPVCollaborat or.java:211)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: A NullPointerException can occur on * * the nodeagent when starting * * TPVLogging for 2 different servers * * at the same time. * **************************************************************** * RECOMMENDATION: * **************************************************************** This was happening because 2 TPVLogging threads were started at the same time for 2 different servers. So the common code was overwritten by both threads separately and causing one thread to loose data to the other.
Problem conclusion
Now the common code has been changed to make sure that data will be maintained for all threads and the NullPointerException will be avoided. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.11 and 9.0.0.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
PI60858
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
2016-04-15
Closed date
2016-07-14
Last modified date
2016-07-14
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