P4
A DESCRIPTION OF THE REQUEST :
The JRE needs a better mechanism for tracking down these errors to the source... The error message reads:
FATAL ERROR in native method: JNI call made with exception pending
At the very least, we should be able to enable logging (a command-line switch?) that prints out a useful message whenever JNI code throws an exception. That way, when we see "JNI call made with exception pending" we just need to track down the last place where the exception was thrown and fix the problem.
See http://forums.java.net/jive/thread.jspa?threadID=388&tstart=0 for a discussion on this topic.
JUSTIFICATION :
It is extremely difficult to track down these problems to the source
###@###.### 2005-2-04 06:01:09 GMT
The JRE needs a better mechanism for tracking down these errors to the source... The error message reads:
FATAL ERROR in native method: JNI call made with exception pending
At the very least, we should be able to enable logging (a command-line switch?) that prints out a useful message whenever JNI code throws an exception. That way, when we see "JNI call made with exception pending" we just need to track down the last place where the exception was thrown and fix the problem.
See http://forums.java.net/jive/thread.jspa?threadID=388&tstart=0 for a discussion on this topic.
JUSTIFICATION :
It is extremely difficult to track down these problems to the source
###@###.### 2005-2-04 06:01:09 GMT