IBM Support

IV20122: VM EXITS WITH ATTACH API THREAD RUNNING

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
    .
    When large numbers of JVMs terminate simultaneously the thread
    "Attach API wait loop" may not terminate cleanly when the JVM
    exits.
    In this case the JVM kills the thread and the JNI function
    DestroyJavaVM() returns JNI_ERR.
    

Local fix

  • disable attach API by setting the "com.ibm.tools.attach.enable"
    system property to "no".
    

Problem summary

  • The attach API cannot shut down due to contention with other
    JVMs for access to attach API files.
    

Problem conclusion

  • This defect will be fixed in:
    7.0.0 SR1
    6.0.1 SR2
    .
    The JVM was updated to retry in the case of contention.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV20122

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    260

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-23

  • Closed date

    2012-04-23

  • Last modified date

    2012-04-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

    J9 COMMON CODE

  • Fixed component ID

    620700127

Applicable component levels

  • R260 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":"6.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 February 2022