Fixes are available
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
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
In the SVC dump, formatted with jdmpview, you will see abend TCB output like this: properties: CAA=0x50c8afec60 CAA CEL level=0x1b EDB=0x5080a055e8 FailingRegisters=true IFA Enabled=no PSW:31=0x70c100080dc6b48 PTHREADID=0x2a25180000000015 Stack direction=up TCB=0x9a35d0 Task Completion Code=0xffffffff940c1000 WEBFLAG2=0x00 associated Java thread: name: Start Level: Equinox Container: cba97760-8f19-493b-a6b9-043aef3137a7 Thread object: org/eclipse/osgi/framework/eventmgr/EventManager$EventThread @ 0x508c1f7a70 Daemon: true ID: 27 (0x1b) Priority: 5 Thread.State: RUNNABLE JVMTI state: ALIVE RUNNABLE Java stack frames: method: int com/ibm/ws/zos/core/internal/ NativeServiceTracker.ntv_getAngelVersion() (Native Method) method: void com/ibm/ws/zos/core/internal/ NativeServiceTracker.populateServiceRegistry(String) source:NativeServiceTracker.java:423 method: void com/ibm/ws/zos/core/internal/NativeServiceTracker.start (org.osgi.framework.BundleContext) source:NativeServiceTracker.java:256
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty for z/OS * **************************************************************** * PROBLEM DESCRIPTION: An ABEND0C1/ABENDS0C1 occurs when * * starting a Liberty server. * **************************************************************** * RECOMMENDATION: * **************************************************************** During Liberty server startup, the server process checks to see which version of the angel process it is using. If the address space containing this Liberty server has been re-used, it may contain a name token pointing to heap storage that was used by a previous instance of a Liberty server. This can occur when the initial pthread-creating task (IPT) of the new Liberty server uses the same TCB address as a previous Liberty server. This is most likely to occur in a BPXAS address space or a batch initiator. It cannot occur when the server is a started task.
Problem conclusion
Code was added to detect when an IPT TCB is re-used in an address space containing a Liberty server, to avoid the ABEND0C1/ABENDS0C1. The fix for this APAR is currently targeted for inclusion in fix pack 18.0.0.2. 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
PI97611
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-04
Closed date
2018-05-21
Last modified date
2018-05-21
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 PROF -
Fixed component ID
5655W6514
Applicable component levels
RCD0 PSY
UP
Document Information
Modified date:
04 May 2022