|
Quick Lists
|
|
Bug ID:
|
6253381
|
|
Votes
|
0
|
|
Synopsis
|
-Xcheck:jni JNI call made with exception pending should be a warning
|
|
Category
|
java:runtime
|
|
Reported Against
|
5.0
|
|
Release Fixed
|
mustang(b40)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
6307699
,
6369565
,
6382189
,
2134110
,
6760147
|
|
Submit Date
|
11-APR-2005
|
|
Description
|
A new -Xcheck:jni check was added in J2SE 5.0 which verifies
that we do not enter JNI while an exception is pending. If
there is a pending exception and a customer is using -Xcheck:jni,
the VM will exit with a fatal error.
This check in general is a customer idea, however since the introduction of
this check, we have encountered several instances in the J2SE libraries
and customer libraries where this condition is true.
The fact that the VM is exiting when this occurs is prohibiting the
continued checking of native code. Most if not all cases that we've
encuntered have been benign and it would have been more beneficial
to simply provide a warning and continue executing.
xxxxx@xxxxx 2005-04-11 17:19:48 GMT
|
|
Work Around
|
N/A
|
|
Evaluation
|
Changed pending exception to warning, adding one more function
NativeReportJNIWarning;
xxxxx@xxxxx 2005-05-30 11:50:45 GMT
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |