IBM Support

IV82515: JAVA THREAD LEAK WHEN USING THREAD-LOCAL STORAGE DESTRUCTORS TO DETACH NATIVE THREADS

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: OutOfMemoryError
    .
    Stack Trace: N/A
    .
    Java thread objects and associated memory are leaked.
    

Local fix

  • Avoid using destructors to detach threads.
    

Problem summary

  • Attaching a native thread to the VM via JNI creates a java
    thread. The native thread should be detached from the VM when it
    exits, in order to destroy the java thread and free memory
    associated with the thread. If the native application relies on
    a thread-local storage destructor to perform the detach when the
    native thread exits, a problem in the VM causes the detach to
    fail. Thus the java thread and associated memory are leaked.
    This may lead to an out of memory condition.
    

Problem conclusion

  • The VM has been corrected in order to run the thread-local
    storage destructor to detach the native thread successfully.
    .
    This APAR will be fixed in the following Java Releases:
       7    SR9 FP40  (7.0.9.40)
       6 R1 SR8 FP25  (6.1.8.25)
       7 R1 SR3 FP40  (7.1.3.40)
       8    SR3       (8.0.3.0)
    .
    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

    IV82515

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    260

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-09

  • Closed date

    2016-03-14

  • Last modified date

    2016-03-14

  • 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

  • R270 PSY

       UP



Document information

More support for: Runtimes for Java Technology
Virtual Machine

Software version: 260

Reference #: IV82515

Modified date: 14 March 2016