PH22759: Abend on the zOS Hard failure Cleanup Thread during server stop processing

APAR status

• Closed as program error.

Error description

• A stop was issued for the Liberty server.   The deactivate
  was driven for a z/OS core service to terminate.  A java
  thread, "zOS Hard failure Cleanup Thread", was released to
  terminate and control was returned to its caller.   The zOS
  Hard failure Cleanup Thread needs to drive native and access
  storage that may well be freed by asynchronous clean
  activity.   This may result in a native ABEND under the JVM
  and produce a javacore.
  
  The javacore will show the following:
  1XMCURTHDINFO  Current thread
  3XMTHREADINFO      "zOS Hard failure Cleanup Thread"
  J9VMThread:0x000000000E864800,
  omrthread_t:0x00000051063CE840,
  java/lang/Thread:0x00000000807A39B8, state:R, prio=5
  3XMJAVALTHREAD            (java/lang/Thread getId:0x2E,
  isDaemon:true)
  3XMTHREADINFO1            (native thread ID:0xDF97800,
  native priority:0x5, native policy:UNKNOWN, vmstate:R, vm
  thread flags:0x00000020)
  3XMCPUTIME               CPU usage total: 0.066000000 secs,
  current category="Application"
  3XMHEAPALLOC             Heap bytes allocated since last GC
  cycle=0 (0x0)
  3XMTHREADINFO3           Java callstack:
  4XESTACKTRACE                at
  com/ibm/ws/zos/core/internal/HardFailureNativeCleanup.ntv_ha
  rdFailureCleanupDeactivate(Native Method)
  4XESTACKTRACE                at
  com/ibm/ws/zos/core/internal/HardFailureNativeCleanup$HardFa
  ilureCleanupThread.run(HardFailureNativeCleanup.java:146)
  3XMTHREADINFO3           No native callstack available on
  this platform
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty for z/OS                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend on the zOS Hard failure Cleanup   *
  *                      Thread during server stop processing    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A stop was issued for the Liberty server.  The deactivate was
  driven for a z/OS core service to terminate.  A java thread,
  "zOS Hard failure Cleanup Thread", was released to terminate and
  control was returned to its caller.   The zOS Hard failure
  Cleanup Thread needs to drive native and access storage that may
  well be freed by asynchronous clean activity.   This may result
  in a native ABEND under the JVM and produce a javacore.
  
  The javacore will show the following:
  1XMCURTHDINFO  Current thread
  3XMTHREADINFO      "zOS Hard failure Cleanup Thread"
  J9VMThread:0x000000000E864800, omrthread_t:0x00000051063CE840,
  java/lang/Thread:0x00000000807A39B8, state:R, prio=5
  3XMJAVALTHREAD            (java/lang/Thread getId:0x2E,
  isDaemon:true)
  3XMTHREADINFO1            (native thread ID:0xDF97800, native
  priority:0x5, native policy:UNKNOWN, vmstate:R, vm thread
  flags:0x00000020)
  3XMCPUTIME               CPU usage total: 0.066000000 secs,
  current category="Application"
  3XMHEAPALLOC             Heap bytes allocated since last GC
  cycle=0 (0x0)
  3XMTHREADINFO3           Java callstack:
  4XESTACKTRACE                at
  com/ibm/ws/zos/core/internal/HardFailureNativeCleanup.ntv_hardFa
  ilureCleanupDeactivate(Native Method)
  4XESTACKTRACE                at
  com/ibm/ws/zos/core/internal/HardFailureNativeCleanup$HardFailur
  eCleanupThread.run(HardFailureNativeCleanup.java:146)
  3XMTHREADINFO3           No native callstack available on this
  platform
  

Problem conclusion

• Code has been modified to synchronize the shutting down of the
  zOS Hard failure Cleanup Thread with the calling thread.
  Control will not be returned to the calling thread until the zOS
  Hard failure Cleanup Thread has completed its call to native
  code for its termination processing.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 20.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 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