IBM Support

PI70346: NULLPROINTEREXCEPTION SEEN IN NODEAGENT SYSTEMERR.LOG DURING TPV PERFORMANCE MONITORING STARTUP

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • As a way to acquire data of server from TPV, the customer uses
    com.ibm.ws.tpv.engine.UserPreferences.
    The NullProinterException can be observed in NodeAgent
    SystemErr.log.
    
    Customer after starting the node agent, application server,
    running a script
    
    
    ---------
    ### Create a logging information of TPV ###
    pref = com.ibm.ws.tpv.engine.UserPreferences()
    #pref = UserPreferences()
    pref.setServerName(v_appserver)
    pref.setNodeName(v_nodeName)
    pref.setRefreshRate(int(v_RefreshRate))
    pref.setBufferSize(int(v_BufferSize))
    pref.setLoggingDuration(int(v_LoggingDuration))
    pref.setLogFileSize(int(v_LogFileSize))
    pref.setNumLogFiles(int(v_NumLogFiles))
    pref.setLogFileName(v_LogFileName)
    params = [pref]
    print params
    
    list = java.util.ArrayList()
    list.add("com.ibm.ws.tpv.engine.UserPreferences")
    sigs = jarray.array(list,java.lang.String)
    #sigs = ["com.ibm.ws.tpv.engine.UserPreferences"]
    
    ### Set the logging information of TPV ###
    print AdminControl.invoke_jmx(perfOName, "monitorServer",
    params, sigs)
    ### Start of logging ###
    print AdminControl.invoke_jmx(perfOName, "startLogging",
    params, sigs)
    ---------
    
    
    Currently when executed against server in the customer's
    environment,
    NullPointerException is generated in
    SystemOut.log/SystemErr.log/trace.log of NodeAgent.
    
    
    Trace is already acquired with NodeAgnet.
    
    <Nodeagent/SystemOut.log>
    [2/26/16 10:17:14:849 JST] 0000007b ServerRJvmCon E
    ServerRJvmConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:14:898 JST] 0000007b ServerRJvmCon E
    ServerRJvmConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:14:909 JST] 0000007b ServerRJvmCon E
    ServerRJvmConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:14:920 JST] 0000007b ServerRJvmCon E
    ServerRDynamicCacheConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:14:932 JST] 0000007b ServerRJvmCon E
    ServerRDynamicCacheConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:14:940 JST] 0000007b ServerRJvmCon E
    ServerRDynamicCacheConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:16:815 JST] 0000007b ServerRSessio E
    SererRSessionConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:16:827 JST] 0000007b ServerRSessio E
    SererRSessionConfigCalc unexpected exception
    java.lang.NullPointerException
    [2/26/16 10:17:16:837 JST] 0000007b ServerRSessio E
    SererRSessionConfigCalc unexpected exception
    java.lang.NullPointerException
    -----
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  8.5.5 and 9.0                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: A NullPointerException occurs when      *
    *                      multiple servers start the Tivoli       *
    *                      Performance Viewer logging at the same  *
    *                      time.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the Tivoli Performance Viewer logging is started
    simultaneously for two different servers on the same node
    agent,
    the common code was overwritten by both threads separately,
    causing
    one thread to lose data to the other. Therefore, a
    NullPointerException occurs, when it tries to get the missing
    data.
    

Problem conclusion

  • The common code has been modified to ensure that it is thread
    safe and synchronized. This makes the data maintained for all
    threads.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.12 and 9.0.0.4.  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

    PI70346

  • 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-10-07

  • Closed date

    2017-03-16

  • Last modified date

    2017-03-16

  • 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

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI70346

Modified date: 16 March 2017


Translate this page: