IV82515: JAVA THREAD LEAK WHEN USING THREAD-LOCAL STORAGE DESTRUCTORS TO DETACH NATIVE THREADS
Closed as program error.
Error Message: OutOfMemoryError . Stack Trace: N/A . Java thread objects and associated memory are leaked.
Avoid using destructors to detach threads.
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.
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 (188.8.131.52) 6 R1 SR8 FP25 (184.108.40.206) 7 R1 SR3 FP40 (220.127.116.11) 8 SR3 (18.104.22.168) . 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/
Reported component name
J9 COMMON CODE
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
J9 COMMON CODE
Fixed component ID
Applicable component levels