IBM Support

PH00435: Collective controller logs NoSuchElementException from LivenessMontiorV2

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • During start up of a collective controller an FFDC is logged
    for a NoSuchElementException from LivenessMontiorV2.  The
    exception does not cause any functional problems.
    
    >Exception = java.util.NoSuchElementException
    >Source =
    com.ibm.ws.collective.repository.internal.monitor.LivenessMo
    nitorV2
    >probeid = 444
    >Stack Dump = java.util.NoSuchElementException: Node
    /sys.was.system/atlas/members/6d104c3d-b3be-493e-820c-644eb2
    e7d549/heartbeat.interval does not exist
    >at
    com.ibm.ws.collective.repository.internal.frappe.FrappeClien
    tImpl.getData(FrappeClientImpl.java:526)
    >at
    com.ibm.ws.collective.repository.internal.CollectiveReposito
    ryMBeanImpl.getData(CollectiveRepositoryMBeanImpl.java:642)
    >at
    com.ibm.ws.collective.repository.internal.monitor.LivenessMo
    nitorV2.loadInitialState(LivenessMonitorV2.java:430)
    >at
    com.ibm.ws.collective.repository.internal.monitor.LivenessMo
    nitorV2.activate(LivenessMonitorV2.java:125)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty - Collectives                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Collective controller logs              *
    *                      NoSuchElementException from             *
    *                      LivenessMontiorV2                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During start up of a collective controller an FFDC is logged for
    a NoSuchElementException from LivenessMontiorV2.  The exception
    does not cause any functional problems.
    
    >Exception = java.util.NoSuchElementException
    >Source =
    com.ibm.ws.collective.repository.internal.monitor.LivenessMonito
    rV2
    >probeid = 444
    >Stack Dump = java.util.NoSuchElementException: Node
    /sys.was.system/atlas/members/6d104c3d-b3be-493e-820c-
    644eb2e7d549/heartbeat.interval does not exist
    >at
    com.ibm.ws.collective.repository.internal.frappe.FrappeClientImp
    l.getData(FrappeClientImpl.java:526)
    >at
    com.ibm.ws.collective.repository.internal.CollectiveRepositoryMB
    eanImpl.getData(CollectiveRepositoryMBeanImpl.java:642)
    >at
    com.ibm.ws.collective.repository.internal.monitor.LivenessMonito
    rV2.loadInitialState(LivenessMonitorV2.java:430)
    >at
    com.ibm.ws.collective.repository.internal.monitor.LivenessMonito
    rV2.activate(LivenessMonitorV2.java:125)
    

Problem conclusion

  • The problem is fixed by making the code more resilient to
    variations in the sequence of events during start up.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 18.0.0.3.  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

    PH00435

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-12

  • Closed date

    2018-07-12

  • Last modified date

    2018-07-12

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels



Document information

More support for: WebSphere Application Server

Software version: CD0

Reference #: PH00435

Modified date: 12 July 2018


Translate this page: