IBM Support

IJ58271: CRASH WHEN CONCURRENT SCAVENGER IN ABORT STATE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: A SIGSEGV event is received
    .
    Stack Trace: {com/ibm/json/java/internal/Serializer.writeObject}
    JIT <OSB>0000000044a88770<CSB>
    {com/ibm/json/java/internal/Serializer.write} JIT
    <OSB>0000000044a88950<CSB>
    {com/ibm/json/java/internal/Serializer.writeObject} JIT
    <OSB>0000000044a889c0<CSB>
    {com/ibm/json/java/internal/Serializer.writeObject} JIT
    <OSB>0000000044a88ba0<CSB>
    {com/ibm/json/java/internal/Serializer.writeObject} JIT
    <OSB>0000000044a88d80<CSB>
    {com/ibm/json/java/internal/Serializer.writeObject} JIT
    <OSB>0000000044a88f60<CSB>
    {com/ibm/json/java/internal/Serializer.writeObject} JIT
    <OSB>0000000044a89140<CSB>
    {com/ibm/zosconnect/internal/ResponseDataHandler.setOutputJson}
    JIT <OSB>0000000044a89320<CSB>
    {com/ibm/zosconnect/internal/ApiManagerImpl.invokeApi} JIT
    <OSB>0000000044a89438<CSB>
    {com/ibm/zosconnect/internal/web/ServiceProxyServlet$3.run} JIT
    <OSB>0000000044a895f0<CSB>
    {com/ibm/ws/webcontainer/async/ServiceWrapper.wrapAndRun} JIT
    <OSB>0000000044a896d0<CSB>
    {com/ibm/ws/webcontainer/async/WrapperRunnableImpl.run} JIT
    <OSB>0000000044a89750<CSB>
    {com/ibm/ws/threading/internal/ExecutorServiceImpl$RunnableWrapp
    er.run} JIT <OSB>0000000044a898b8<CSB>
    {java/util/concurrent/ThreadPoolExecutor.runWorker} JIT
    <OSB>0000000044a89920<CSB>
    {java/lang/Thread.run} JIT <OSB>0000000044a89a00<CSB>
    {libj9jit29.so}{ZreturnFromJIT0} <OSB>0x97fd<CSB>
    .
    

Local fix

  • The issue can be worked around by removing JVM option
    -Xgc:concurrentScavenge
    

Problem summary

  • The problem is caused when concurrent scavenge is in abort state
    and the read barrier is wrongly disabled.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IJ58271

  • Reported component name

    JIT

  • Reported component ID

    620700124

  • Reported release

    290

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2026-05-09

  • Closed date

    2026-05-09

  • Last modified date

    2026-05-09

  • 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

    JIT

  • Fixed component ID

    620700124

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
10 May 2026