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

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 SR12FP5
  .
  The JIT compiler was changed such that any area where a thread
  death exception resulting from a Thread.stop() call could be
  thrown would be able to unlock any objects held by the thread
  being terminated.
  .
  To obtain the fix:
  Install build 20110502 or later
  

Temporary fix

Comments

APAR Information

• 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

  JAVA 5 JIT

• Fixed component ID

  620500124

Applicable component levels

• R500 PSY

     UP