JDK-2121379 : JNI violations in I/O classes
  • Type: Backport
  • Backport of: JDK-4803744
  • Component: core-libs
  • Sub-Component: java.io
  • Priority: P1
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2004-11-12
  • Updated: 2011-03-24
  • Resolved: 2004-11-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 Availability Release.

To download the current JDK release, click here.
Other
1.4.2_07 b03Fixed
Description
FATAL ERROR in native method: JNI call made with exception pending
	at java.io.ObjectStreamClass.hasStaticInitializer(Native Method)

-----------------  lwp# 1 / thread# 1  --------------------
 ce4ff317 _lwp_kill (1, 6) + c
 ce5607de thr_kill (1, 6) + 1e
 ce517a9d raise    (6) + 2a
 ce50012e abort    () + ee
 ce7ed1c0 void os::abort(int) (1) + 70
 ce75ec2c void ReportJNIFatalError(JavaThread*,const char*) (808afe8, ce86bb00) + 3c
 ce75ecf8 void NativeReportJNIFatalError(JavaThread*,const char*) (808afe8, ce86bb00) + 78
 ce76340c checked_jni_IsInstanceOf (808b080, 81cfc40, 811e2a8) + 354
 ce2cef72 Java_java_io_ObjectStreamClass_hasStaticInitializer () + f2
 00000000 ???????? ()

NB this native is in libjava in 1.4.2

So we can find this when we search.
###@###.### 2005-03-22 15:30:33 GMT
Comments
EVALUATION Problem in ObjectStreamClass.c native method Java_java_io_ObjectStreamClass_hasStaticInitializer caused bugs 6193413 and 6179378 detected by changes for bug 5101288 with -Xcheck:jni. ###@###.### 2004-11-15 19:43:18 GMT -------------------------------------------------------- These test failure don't seem to be due to -Xcheck:jni improvements fix(done in 1.4.2_07b02) or due to the I/O classes changes to fix jni violations(1.4.2_07b03). * I saw the failure even without -Xcheck:jni. mach:/home/pb131437 106 % which java /net/latte.ireland/deployment4/jdk/1.4.2_07b03/solaris-sparc/bin/java java javasoft.sqe.tests.api.java.lang.Thread.stopTests Thread1801: Passed. OKAY Thread1802: Passed. OKAY Thread1803: Failed. stopped thread ran as usual Thread1804: Failed. timeout 2 Thread1805: Passed. OKAY Thread1806: Passed. OKAY Thread1807: Failed. Test case throws exception: java.security.AccessControlException: access denied (java.lang.RuntimePermission createSecurityManager) Wait until state=0 Wait until state=1 STATUS:Failed.test cases: 7; passed: 4; failed: 3; first test case failure: Thread1803 * I saw the same failures with 1.4.2_07b01 also: mach:/home/pb131437 108 % which java /net/latte.ireland/deployment4/jdk/1.4.2_07b01/solaris-sparc/bin/java java -Xcheck:jni javasoft.sqe.tests.api.java.lang.Thread.stopTests Thread1801: Passed. OKAY Thread1802: Passed. OKAY Thread1803: Failed. stopped thread ran as usual Thread1804: Failed. timeout 2 Thread1805: Passed. OKAY Thread1806: Passed. OKAY Thread1807: Failed. Test case throws exception: java.security.AccessControlException: access denied (java.lang.RuntimePermission createSecurityManager) Wait until state=0 Wait until state=1 STATUS:Failed.test cases: 7; passed: 4; failed: 3; first test case failure: Thread1803 ###@###.### 2004-11-26 05:24:08 GMT I have created a new bug/CR for this issue as this bug is different from the issues in the above jck tests: 6201185. I have also reset this to fix-delivered as the original problem addressed by this bug ( as seen in 6193413 ) is fixed. ###@###.### 2004-11-29 17:41:50 GMT All JCK runtime tests now pass with -Xcheck:jni flag bar one. This is now targeted for 1.4.2_08. (CR 2121822) ###@###.### 2004-12-14 16:44:44 GMT
15-11-2004