Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6253381

-Xcheck:jni JNI call made with exception pending should be a warning

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 5.0, 6
    • Fix Version/s: 6
    • Component/s: hotspot
    • Subcomponent:
    • Resolved In Build:
      b40
    • CPU:
      generic, sparc
    • OS:
      generic, solaris

      Backports

        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 good 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.


        ###@###.### 2005-04-11 17:19:48 GMT

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ksrini Kumar Srinivasan
                  Reporter:
                  bobv Bob Vandette
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Imported:
                    Indexed: