IBM Support

PI59076: S0C4-38 ABEND FROM OUT OF A JVM METHOD GETORIGINALROMMETHOD+4A

Fixes are available

8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During normal operation, a WebSphere controller JVM abended with
    S0C4-38. LE call stack on the TCB which abended:
    Entry                      E  Offset  Statement   Load Mod
    getOriginalROMMethod       +0000004A              *PATHNAM
    walkBytecodeFrame          +00000108              *PATHNAM
    walkStackFrames            +00000A60              *PATHNAM
    walkStackForExceptionThrow +00000098              *PATHNAM
    SIDECARINVOKEREFLECTMETHOD -000306AE              *PATHNAM
    JVM_InvokeMethod           +000000AA              *PATHNAM
    Java_sun_reflect_NativeMethodAccessorImpl_invoke0
                               +0000002A              *PATHNAM
    RUNJAVATHREAD              +00000000              *PATHNAM
    javaProtectedThreadProc    +0000010A              *PATHNAM
    j9sig_protect              +0000076E              *PATHNAM
    javaThreadProc             +00000072              *PATHNAM
    thread_wrapper             +00000562              *PATHNAM
    CELQPCMM                   +00000F80              CELQLIB
    In the dump, this TCB 7477f0 is known as ZAioThreadPool : 0
    associated java thread:
    name:          ZAioThreadPool : 0
    Thread object: com/ibm/ws/util/ThreadPool$DecoratedZOSWorker
                   @0x12812cdd8
    Daemon:        true
    ID:            822 (0x336)
    Priority:      5
    Thread.State:  RUNNABLE
    JVMTI state:   ALIVE RUNNABLE
    Java stack frames:
      bp: 0x0000000034692290
      method: boolean com/ibm/ws390/ziop/
    .
    ZIOPCPPUtilities.process_outbound_async_connect_response(long,
          byte[], int, int)  (Native Method)
          objects: 0x13ad68060
         <corrupt data encountered>
    .
    A variation native call stack could be:
    walkStackFrames+00000A7A              Exception
    GC_VMThreadStackSlotIterator::scanSlots(J9VMThread*,J9VMThre+000
    000BE
    MM_RootScanner::scanOneThread(MM_EnvironmentModron*,J9VMThre+000
    00146
    MM_RootScanner::scanThreads(MM_EnvironmentModron*)+000000F8
    MM_RootScanner::scanRoots(MM_EnvironmentModron*)+0000030E
    MM_ParallelScavenger::workThreadGarbageCollect(MM_Environmen+000
    00130
    MM_ParallelScavengeTask::run(MM_EnvironmentModron*)+00000016
    MM_ParallelDispatcher::slaveEntryPoint(MM_EnvironmentModron*+000
    000F0
    dispatcher_thread_proc2(J9PortLibrary*,void*)+0000013A
    j9sig_protect+0000076E
    dispatcher_thread_proc+00000058
    thread_wrapper+00000562
    CELQPCMM+00000F80
    -
    In each dump of the problem, JNI method
    com/ibm/ws390/ziop/
    ZIOPCPPUtilities.process_outbound_async_connect_response(long,
    byte[], int, int)  (Native Method)
    was on the thread that abended, or was currently running on
    another thread in the jvm.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5 for z/OS.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere controller JVM abended with   *
    *                      ABEND0C4/ABENDS0C4 reason code 38       *
    *                      because a native method did not catch   *
    *                      a native system exception.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The native routine that implements
    ZIOPCPPUtilities.process_outbound_async_connect_response
    called a routine to map the IOR. The map IOR routine
    threw a CORBA::BAD_PARAM system exception with error code
    C9C2C313 because the locate IOR was 0. There is no native try
    catch around the call to the map IOR routine so it blows back
    to the previous native routine on the stack. The previous
    native routine on the stack was
    Java_com_ibm_ws390_xmem_XMemCRCppUtilities_setupThread. It
    catches the native exception creates an Exception For Java and
    goes back to java which hits the exception. Not handling the
    native exception resulted in the JVM encountering
    an 0c4 reason code 38 abend.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI59076

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-14

  • Closed date

    2016-05-23

  • Last modified date

    2016-05-23

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 December 2021