Fixes are available
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
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
RCD0 PSY
UP
Document Information
Modified date:
04 May 2022