Closed as program error.
Error Message: The application hangs, i.e., no progress is made by the application, with no error message. . Stack Trace: N/A .
-Xjit:disableAsyncCheckRemoval works around this problem but it may cause slight performance degradation.
This problem may occur when a trusted method (i.e., a method in String, HashMap, or TreeMap classes) that contains a loop is inlined in user code. With low probability, the JIT generates a code for the user loop that doesn't have a GC point. Now if other threads are waiting for GC to happen, and the user code doesn't progress until something happens in the other threads, there will be a deadlock. In other words, GC is waiting for user loop which is waiting for other threads which are waiting for GC.
This defect will be fixed in: 7.0.0 SR2 6.0.0 SR11 6.0.1 SR3 5.0.0 SR14 . The check that JIT uses to detect whether a loop has come from a trusted method has been made more accurate.
Reported component name
Reported component ID
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
Fixed component ID
Applicable component levels