VOOZH about

URL: https://www.ibm.com/support/pages/apar/IV74444

⇱ IV74444: UNHANDLED EXCEPTION DURING AOT COMPILATION OR IN AOT COMPILED ME THOD


IV74444: UNHANDLED EXCEPTION DURING AOT COMPILATION OR IN AOT COMPILED ME THOD

APAR status

  • Closed as program error.

Error description

  • Error Message: An unhandled exception is raised with varying
    symptoms: Segmentation error during AOT compilation with
    vmState=0x0005ff05, segmentation error or illegal instruction in
    an AOT compiled method with vmState=0x00000000. This happens
    when trying to AOT compile or execute an AOT compiled method
    that inlines java/util/concurrent/ConcurrentLinkedQueue.poll or
    java/util/concurrent/ConcurrentLinkedQueue.offer .
    .
    Stack Trace: findFieldInTable
    findField
    instanceFieldOffset
    TR_J9SharedCacheVM::getInstanceFieldOffset
    TR_J9VM::getInstanceFieldOffset
    inlineConcurrentLinkedQueueTMPoll
    TR_J9VMBase::inlineDirectCall
    TR_S390TreeEvaluator::directCallEvaluator
    TR_CodeGenerator::evaluate
    TR_S390TreeEvaluator::treetopEvaluator
    TR_CodeGenerator::evaluate
    TR_CodeGenerator::doInstructionSelection()
    Or a failure in a compiled method.
    .
    This problem is only triggered on z Systems (both z/OS and
    Linux) if the shared class cache is enabled and transactional
    memory is supported by OS and hardware. It is most likely to be
    seen when using the option -Xtune:virtualized .
    

Local fix

  • This problem can be avoided by setting the JVM option
    -Xaot:dontInline={java/util/concurrent/ConcurrentLinkedQueue.*}.
    Note that this can impact performance.
    

Problem summary

  • The issue was in the crafted fast path instruction sequences
    that are supposed to optimize
    java/util/concurrent/ConcurrentLinkedQueue.poll or
    java/util/concurrent/ConcurrentLinkedQueue.offer; the JIT
    compiler did not support the possibility that during
    Ahead-Of-Time (AOT) method compilations, some of the class
    pointers may not be available.
    

Problem conclusion

  • The JIT compiler has been updated to handle this case properly.
    .
    This APAR will be fixed in the following Java Releases:
     8 SR1 FP10 (8.0.1.10)
    .
    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

    IV74444

  • Reported component name

    JIT

  • Reported component ID

    620700124

  • Reported release

    130

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-22

  • Closed date

    2015-06-22

  • Last modified date

    2015-06-22

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

  • Fixed component name

    JIT

  • Fixed component ID

    620700124

Applicable component levels

  • R130 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC9HBA","label":"Just In Time (JIT) Compiler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"130","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
22 June 2015