PI60858: NullPointerExceptions on NodeAgent when starting TPVLogging via wsadim for 2 different servers at the same time

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI60858: NullPointerExceptions on NodeAgent when starting TPVLogging via wsadim for 2 different servers at the same time

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?