IZ86766: JVM CRASHES WHEN A THREAD CALLS DESTROYJAVAVM() WITHOUT FIRST BE ING ATTACHED

APAR status

• Closed as program error.

Error description

• Error Message:
  .
  Stack Trace: ntdll!KiUserExceptionDispatcher+0x4
      J9THR24!j9thread_monitor_enter(struct J9ThreadMonitor *
  monitor = 0x00000000)+0x19
      j9vm24!DestroyJavaVM(struct JNIInvokeInterface_ ** javaVM =
  0x00000000)+0x46
      jvm!DestroyJavaVM(struct JNIInvokeInterface_ ** javaVM =
  0x00000000)+0xc
      <SOME_APPLICATION_CODE>
  .
  

Local fix

• This issue can be worked around by calling AttachCurrentThread()
  before calling DestroyJavaVM().
  

Problem summary

• If the thread that is issuing the DestroyJavaVM() call is not
  attached to the JVM there is a failure to enter a JVM resource.
  JNI specification details that as of 1.2 any thread, whether
  attached or not, can call this function.
  

Problem conclusion

• This defect will be fixed in:
  6.0.0 SR9
  .
     The JVM has been updated such that the thread calling
  DestroyJavaVM() will not have a failure obtaining JVM resources.
  .
  To obtain the fix:
  Install build 20101022 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

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R600 PSN

     UP