IBM Support

IV44173: JAVA JIT - HANG INSIDE A LOOP DUE TO A FAILURE TO YIELD FOR A GC CYCLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: N/A
    .
    Stack Trace: N/A
    .
    N/A
    

Local fix

  • -Xjit:disableRedundantAsyncCheckRemoval would work around the
    functional issue
    

Problem summary

  • Internal testing has uncovered a functional bug (hang) due to
    improper placement of asyncchecks. This leads to a hang when we
    wait for a particular thread to yield and it gets stuck inside a
    loop (while this bug can happen anywhere with the necessary
    bytecode pattern we have only seen it in ForkJoin code) not
    being able to yield because there is no asynccheck.
    

Problem conclusion

  • This defect will be fixed in:
    7.0.0 SR5
    6.0.1 SR6
    6.0.0 SR14
    5.0.0 SR16
    .
    The JIT has been updated to eliminate the problem with async
    check placement.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV44173

  • Reported component name

    JAVA 5 JIT

  • Reported component ID

    620500124

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-12

  • Closed date

    2013-06-12

  • Last modified date

    2013-06-12

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

    IV44172

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

Fix information

  • Fixed component name

    JAVA 5 JIT

  • Fixed component ID

    620500124

Applicable component levels

  • R500 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":"5.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
12 June 2013