Exceptions when using SharedLock and SharedCondition created without the IN_PROCESS_ONLY flag

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • mvm-7
    • Affects Version/s: mvm-7
    • Component/s: hotspot
    • None
    • team
    • x86
    • linux

      Several exceptions occur when using SharedLock and SharedCondition created without the IN_PROCESS_ONLY flag for an InProcessIsolate.

      To reproduce run the attached program.


      java.lang.IllegalMonitorStateException: The current thread is not holding the lock
              at sun.shared.CrossProcessLock.unlock0(Native Method)
              at sun.shared.CrossProcessLock.unlock(CrossProcessLock.java:77)
              at pingpong.Producer.main(Producer.java:43)


      Exception in thread "main"
      java.lang.UnknownError: System call semop failed with errno = 22
              at sun.shared.CrossProcessLock.lock0(Native Method)
              at sun.shared.CrossProcessLock.lock(CrossProcessLock.java:52)
              at pingpong.Producer.main(Producer.java:40)

      Exception in thread "main"
      java.lang.NullPointerException
              at java.util.regex.Matcher.getTextLength(Matcher.java:1233)
              at java.util.regex.Matcher.reset(Matcher.java:308)
              at java.util.regex.Matcher.<init>(Matcher.java:228)
              at java.util.regex.Pattern.matcher(Pattern.java:946)
              at sun.shared.ResourceID.<init>(ResourceID.java:116)
              at com.sun.shared.Uid.<init>(Uid.java:47)
              at sun.shared.CrossProcessCondition.getLock(CrossProcessCondition.java:139)
              at pingpong.Consumer.main(Consumer.java:23)

            Assignee:
            Keith Mcguigan (Inactive)
            Reporter:
            Kinsley Wong (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: