IBM Support

PH23817: GPF IN LIBERTY SERVER DURING SHUTDOWN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The liberty server received gpf during termination.
    The JNI call from libzNativeServices.so:onThreadEnd caused
    this
    gpf due to the bogus jobject parameter.
    .
    Traceback:
    DSA     Entry           E Offset   UnService Status
    ......
    21      runCallInMethod +0000042C  j201911 Exception
    22      gpProtectedRunCallInMethod(void*)
    +000000BC  j201911 Call
    23      gpCheckCallin   +0000004C  j201911 Call
    24      callVirtualVoidMethod
    +00000046  j201911 Call
    25      onThreadEnd     +00000040          Call
    26      jvmtiHookThreadEnd
    +0000011E  j201911 Call
    27      J9HookDispatch(J9HookInterface**,unsigned
    long,void*)
    +0000029C  j201911 Call
    28      javaProtectedThreadProc
    +000002BC  j201911 Call
    29      omrsig_protect
    +000008CA  j201911 Call
    30      javaThreadProc  +0000008C  j201911 Call
    31      thread_wrapper  +000009BA  j201911 Call
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty for z/OS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND0C4/ABENDS0C4 during server stop   *
    *                      when native routine onThreadEnd calls   *
    *                      Java routine threadTerminating()        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ABEND0C4/ABENDSOC4 during server stop when native routine
    libzNativeServices.so:onThreadEnd calls Java routine
    ThreadTracker.threadTerminating(). The abend happens because the
    global reference to the Java object was deleted before making
    the call to ThreadTracker.threadTerminating().
    
    syslog showed
    JVMDUMP039I Processing dump event "gpf", detail "" at
    2020/03/25
    followed by a transaction dump.
    Following is the traceback of the abending thread taken from the
    transaction dump.
    
    Information for thread 1904B0000000033D
    TCB Address: 008B63C8
    CAA Address: 00000052_1F7FEC60
    PCB Address: 00000050_00103E28
    
    Traceback:
    DSA      Entry       E  Offset  Statement   Load Mod
    Program
    
    1        _TDUMP      +000000C2
    _TDUMP
    
    ...
    
     19      CEEOSIGG   +00000000             CELQLIB
    CEEOSIGG HLE77A0 Call
     20      CELQHROD   +00000266             CELQLIB
    CELQHROD HLE77A0 Call
     21      runCallInMethod
                          +0000042C             *PATHNAM
    j201911 Exception
     22      gpProtectedRunCallInMethod(void*)
                          +000000BC             *PATHNAM
    j201911 Call
     23      gpCheckCallin
                          +0000004C             *PATHNAM
    j201911 Call
     24      callVirtualVoidMethod
                          +00000046             *PATHNAM
    j201911 Call
     25      onThreadEnd +00000040             *PATHNAM
    Call
     26      jvmtiHookThreadEnd
                          +0000011E             *PATHNAM
    j201911 Call
     27      J9HookDispatch(J9HookInterface**,unsigned long,void*)
                          +0000029C             *PATHNAM
    j201911 Call
     28      javaProtectedThreadProc
    +000002BC             *PATHNAM                      j201911 Call
    29      omrsig_protect
    +000008CA             *PATHNAM                      j201911 Call
    30      javaThreadProc
                          +0000008C             *PATHNAM
    j201911 Call
     31      thread_wrapper
                          +000009BA             *PATHNAM
    j201911 Call
     32      CELQPCMM   +00000F80             CELQLIB
    CELQPCMM UI33702 Call
    

Problem conclusion

  • Updated the code to not call ThreadTracker.threadTerminating()
    or ThreadTracker.threadStarted() after deleting the global
    reference.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 20.0.0.4.  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

    PH23817

  • 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

    2020-03-29

  • Closed date

    2020-04-07

  • Last modified date

    2020-04-07

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"CD0"}]

Document Information

Modified date:
15 September 2021