JDK-5101288 : async exception can be delivered on entry from native to vm
  • Type: Bug
  • Status: Closed
  • Resolution: Fixed
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P2
  • Affected Version: 6
  • OS: generic
  • CPU: generic
  • Submit Date: 2004-09-13
  • Updated Date: 2012-10-09
  • Resolved Date: 2004-09-29
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
Other JDK 6
1.4.2_07Fixed 6Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Description
There is a chance for an async exception to be delivered on entry from native to
vm due to a safepoint. This violates the JNI spec.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.5.0_01 mustang FIXED IN: mustang INTEGRATED IN: 1.5.0_01
2004-09-29

PUBLIC COMMENTS Integrated fix into Tiger Update 1 Build 03
2004-09-29

EVALUATION Async exceptions can be installed on the entry from native to vm. This can cause JNI functions to be called with a pending exception. The fix fixes all such places to not install async exceptions as pending exceptions, including: - ThreadInVMfromNative() - SafepointSynchronize::block() - JavaThread::send_thread_stop() ###@###.### 2004-09-16
2004-09-16