PH35542: ABEND 0C4 IN NTV_REGISTERSERVER REPORTED ON WEBSPHERE LIBERTY Z/OS 20.0.0.12 (WLP-1.0.47.CL201220201111-0736)

APAR status

• Closed as program error.

Error description

• Java stack frames:
  bp: 0x0000000060ebb4b8 method: int com/ibm/
  ws/zos/core/internal/NativeServiceTracker.ntv_registerServer
  (Str
  ing, String) (Native Method)
  objects: 0x8fafadc8 0x8fb0ae38
  0x8fb08b50
  bp: 0x0000000060ebb4e8 method: int com/ibm/ws/zos/co
  re/internal/NativeServiceTracker.registerServer(String)
  source:
  NativeServiceTracker.java:510
  objects: <no objects in this
  frame>
  bp: 0x0000000060ebb548 method: void com/ibm/ws/zos/core/
  internal/NativeServiceTracker.start(org.osgi.framework.Bundl
  eCon
  text) source: NativeServiceTracker.java:261
  objects:
  0x8fafadc8 0x80868358 0x8fb08b50
  bp: 0x0000000060ebb570
  method: void
  com/ibm/ws/zos/core/internal/CoreBundleActivator.ac
  tivate(org.osgi.framework.BundleContext) source:
  CoreBundleActivator.java:112
  objects: 0x8fa46c88
  0x80868358
  
  
  LE Native Stack:
  
  CEEHDSP+0xa3da88c0 (,
  0x0000000000000000)
  CEEOSIGJ+0xa3af94b0 (, 0x0000000000000000)
  
  CELQHROD+0xa3d94f78 (, 0x0000000000000000)
  
  CEEOSIGG+0xa3b004d0 (, 0x0000000000000000)
  
  CELQHROD+0xa3d94f78 (, 0x0000000000000000)
  
  ntv_registerServer+0x9f993488 (, 0x0000000000000000)
  
  FFISYS+0xa24619a8 (, 0x0000000000000000)
  ffi_call+0xa220e308
  (, 0x0000000000000000)
  bytecodeLoopCompressed+0xa23a0208 (,
  0x0000000000000000)
  ZJ9SYM1+0xa2461cf8 (, 0x0000000000000000)
  
  sidecarInvokeReflectMethodImpl+0xa244ec18 (,
  0x0000000000000000)
  sidecarInvokeReflectMethod+0xa244ce60 (,
  0x0000000000000000)
  JVM_InvokeMethod_Impl+0x9feaf370 (,
  0x0000000000000000)
  JVM_InvokeMethod+0xa249bc48 (,
  0x0000000000000000)
  JVM_InvokeMethod+0xa24eca98 (,
  0x0000000000000000)
  
  Java_sun_reflect_NativeMethodAccessorImpl_invoke0+0xa2178788
  (, 0x0000000000000000)
  ZJ9SYM1+0xa2461cf8 (,
  0x0000000000000000)
  runJavaThread+0xa24552a0 (,
  0x0000000000000000)
  javaProtectedThreadProc+0xa23a7e10 (,
  0x0000000000000000)
  omrsig_protect+0xa20f0668 (,
  0x0000000000000000)
  javaThreadProc+0xa23a43d8 (,
  0x0000000000000000)
  thread_wrapper+0xa21c3f98 (,
  0x0000000000000000)
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty for z/OS                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND 0C4 in native routine             *
  *                      ntv_registerServer during               *
  *                      initialization of the Server            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The ABEND0C4/ABENDS0C4 occurred in an inlined routine,
  connectUnauthorizedCEnv().  Inside of this routine it detected
  that a NameToken value existed for the current IPT (special TCB
  owning resources for a set of sub-tasks) which points to Liberty
  created C-Environment storage (ex. C userheap).  An ABENDS0C4
  was taken referencing the __csetheapuserdata using the data
  structures pointed to by the NameToken ("BBGZ_KEY8_MC" + IPT TCB
  Address).
  
  The reason for the ABEND is that the referenced storage had been
  released previously.   It turns out the IPT TCB had been used
  previously in the long lived address space; which had started
  and stopped (or canceled) Liberty servers.   Each Liberty server
  will run under its own IPT TCB.   When the previous use of the
  IPT TCB went through termination, storage owned by that TCB was
  released by z/OS.   When that IPT TCB was re-used for a new
  Liberty server that NameToken from it's previous Liberty server
  was found.   This is not usually the case.   Liberty has an
  atExit() routine to release this NameToken.   However, the
  atExit() can be skipped depending upon the environment and the
  way the Server is terminated.  It was skipped in this failing
  scenario.
  

Problem conclusion

• Code has been modified in the inlined routine to verify that the
  IPT TCB has been re-used and as such the portions of the storage
  related to the C-Environment that we manage was already release
  and should not be referenced.   Code has been added to this path
  to rebuild these storage areas to proceed with a normal Liberty
  server initialization.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 21.0.0.5.  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 PROFILE

• Fixed component ID

  5724J0814

Applicable component levels