IBM Support

IJ06288: AN ASSERTION AT JVM SHUTDOWN TIME WITH CONCURRENT SCAVENGER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: The following assertion might be triggered at JVM
    shutdown when a user is running with -Xgc:concurrentScavenge
    option and on a machine with high number of cores or with
    -Xgcthreads option set to run with large number of GC threads:
    CS not in progress, found a object in Survivor: slot 0X.. object
    0x..
    j9mm.141    *   ** ASSERTION FAILED ** at
    StandardAccessBarrier.cpp:701: ((false))
    .
    Stack Trace: MM_StandardAccessBarrier::preObjectRead at
    StandardAccessBarrier.cpp:700
    internalPreReadObject at ObjectAccessBarrierAPI.hpp:2810
    preIndexableObjectReadObject at ObjectAccessBarrierAPI.hpp:2114
    inlineIndexableObjectReadObject at
    ObjectAccessBarrierAPI.hpp:1819
    aaload at BytecodeInterpreter.hpp:5654
    VM_BytecodeInterpreter::run at BytecodeInterpreter.hpp:9262
    bytecodeLoop at BytecodeInterpreter.cpp:100
    c_cInterpreter () at xcinterp.s:150
    cleanUpAttachedThread at callin.cpp:459
    protectedDestroyJavaVM at jniinv.c:336
    omrsig_protect at omrsignal.c:394
    DestroyJavaVM (javaVM=0x7f1170011940) at jniinv.c:498
    DestroyJavaVM (javaVM=0x7f1170011940) at jvm.c:562
    JavaMain ()
    start_thread
    clone ()
    .
    

Local fix

  • This is issue can be avoided by removing -Xgc:concurrentScavenge
    option. This might cause some performance degradation in
    throughput and consistency of response-times as it will disable
    Concurrent Scavenger.
    

Problem summary

  • This problem is caused by a special case with initializing
    internal structures for Concurrent Scavenger.
    

Problem conclusion

  • The JVM has been updated to handle this initialization case
    correctly in Concurrent Scavenger.
    .
    This APAR will be fixed in the following Java Releases:
       8    SR5 FP16  (8.0.5.16)
    .
    Contact your IBM Product's Service Team for these Service
    Refreshes and Fix Packs.
    For those running stand-alone, information about the available
    Service Refreshes and Fix Packs can be found at:
               https://www.ibm.com/developerworks/java/jdk/
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ06288

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    270

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-08

  • Closed date

    2018-05-10

  • Last modified date

    2018-05-10

  • 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

    J9 COMMON CODE

  • Fixed component ID

    620700127

Applicable component levels

  • R270 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
22 February 2022