IBM Support

PI87542: DURING NODEAGENT STARTUP NULLPOINTEREXCEPTION IN WORKPROFILERHAMANAGEDITEM, ISSUE CAN BE IGNORED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • NullPointerException during nodeagent start with following
    call
    stack:
    [17/09/14 23:39:17:020 JST]     FFDC
    Exception:java.lang.NullPointerException
    SourceId:com.ibm.ws.xd.workprofiler.impl.WorkProfilerHAManag
    edIt
    em
    ProbeId:390 java.lang.NullPointerException
    at
    com.ibm.ws.xd.workprofiler.impl.WorkProfilerHAManagedItem.de
    acti
    vate(Wor
    kProfilerHAManagedItem.java:249)
    at
    com.ibm.ws.xd.hamitem.HAManagedItemSupport.disableItem(HAMan
    aged
    ItemSupp
    ort.java:488)
    at
    com.ibm.ws.xd.hamitem.HAManagedItemSupport$BBMessageListener
    .del
    ayedUpda
    ted(HAManagedItemSupport.java:1670)
    at
    com.ibm.ws.xd.hamitem.HAManagedItemSupport$BBMessageListener
    $BBU
    pdateWra
    pper.run(HAManagedItemSupport.java:1567)
    at
    com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
    
    This is a benign error and will not cause any other problem
    in the system. It is present due to a small timing window that
    may be encountered when attempting to deactivate an instance
    of the WorkProfilerHAManagedItem which should not be active
    and will subsequently be deactivated in another code path.
    

Local fix

  • N/A, the error can be ignored
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WAS ND edition- Virtual              *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException in                 *
    *                      WorkProfilerHAManagedItem during        *
    *                      nodeagent start                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    NullPointerException during nodeagent start with following call
    stack:
    [17/09/14 23:39:17:020 JST]     FFDC
    Exception:java.lang.NullPointerException
    SourceId:com.ibm.ws.xd.workprofiler.impl.WorkProfilerHAManagedIt
    em ProbeId:390
    java.lang.NullPointerException
    at
    com.ibm.ws.xd.workprofiler.impl.WorkProfilerHAManagedItem.deacti
    vate(WorkProfilerHAManagedItem.java:249)
    at
    com.ibm.ws.xd.hamitem.HAManagedItemSupport.disableItem(HAManaged
    ItemSupport.java:488)
    at
    com.ibm.ws.xd.hamitem.HAManagedItemSupport$BBMessageListener.del
    ayedUpdated(HAManagedItemSupport.java:1670)
    at
    com.ibm.ws.xd.hamitem.HAManagedItemSupport$BBMessageListener$BBU
    pdateWrapper.run(HAManagedItemSupport.java:1567)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
    This is a benign error and will not cause any other problem in
    the system. It is present due to a small timing window that may
    be encountered when attempting to deactivate an instance of the
    WorkProfilerHAManagedItem which should not be active and
    will be subsequently deactivated in another code path.
    The WorkProfilerHAManagedItem is always started and quickly
    learns that it should be deactivated because there is a better
    process to run the WorkProfilerHAManagedItem. The deactivate
    encounters the exception because the process is not yet
    completely initialized. As a result, the mbean is not
    deactivated immediately. However, subsequent processing will
    perform the same check and deactivate the process if it is not
    needed and at that time the deactivate will succeed because
    the initialization has completed.
    

Problem conclusion

  • The code was improved to remove the small timing window that
    causes the exception.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.13 and 9.0.0.6.  Please refer to the Recommended
    Updates page for delivery information:
    
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Ignore the error as it causes no problem.
    

Comments

APAR Information

  • APAR number

    PI87542

  • 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-09-19

  • Closed date

    2017-09-27

  • Last modified date

    2017-10-10

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021