IV00017: USE OF THREAD.STOP() MAY CAUSE OBJECTS TO REMAIN LOCKED.

Subscribe

You can track all active APARs for this component.

APAR status

Closed as program error.

Error description

Error Message: An object may become locked by a thread that no
longer exists causing other threads to hang by waiting for the
object to become unlocked.
.
Stack Trace: N/A
.
This issue is only present if the deprecated method
Thread.stop() is used.

Local fix

-Xjit:disableRedundantAsyncCheckRemoval

Problem summary

In JIT compiled code, there are certain code regions that were
not capable of unlocking objects held by the thread destroyed by
the Thread.stop() method.

Problem conclusion

This defect will be fixed in:
5.0.0 SR13
6.0.0 SR10
6.0.1 SR1
.
The JVM was modified to prevent throwing the exception from
async check points in the jit, and only throws from the method
enter check.
.
To obtain the fix:
Install build 20110502 or later