HotSpot 2.0,No exception thrown when MonitorExit is called without MonitorEnter

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 2.0
    • Affects Version/s: 2.0
    • Component/s: hotspot
    • None
    • rc1
    • x86
    • generic

      HotSpot 2.0 Server VM RC1 build E fails to throw a "current thread not owner" exception when JNI MonitorExit is called on an object without calling MonitorEnter on that same object.

      STEPS TO REPRODUCE
      - Install JDK 1.2.2.
      - Install HotSpot 2.0 Server VM RC1 build E on JDK 1.2.2.
      - Run JNIMonitortest functional test

      RESULT
      NegativeTest2 and NegativeTest4 both fail because the "current thread not owner" exception is not thrown.

      HotSpot VM Client 1.3 FCS build O and the JDK 1.2.2 classic VM both return the "current thread not owner" exception.

      The JNIMonitorTest can be found at:

      /net/sqesvr/vsn/testbase/other_test_tools/testtools/MonitorTest

      To run the test, execute the runfmix.bat batch script in the MonitorTest directory (That will run the JNI Monitor functional tests). The failure is reproducible.

            Assignee:
            Lars Bak (Inactive)
            Reporter:
            Philip Chin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: