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

findThread() failure on resumeAllThreads: nsk/jdb/suspend/suspend001

    Details

    • Subcomponent:
    • Introduced In Build:
      b10
    • Introduced In Version:
      6
    • Resolved In Build:
      b23
    • CPU:
      generic
    • OS:
      generic

      Description

      I found a place where a resumeAllThreads close to VM exit can cause
      the following error:


      main[1] cont

      > JDWP exit error JVMTI_ERROR_OUT_OF_MEMORY(110): entry in thread table [../../../src/share/back/threadControl.c:1206]

      FATAL ERROR in native method: JDWP entry in thread table, jvmtiError=JVMTI_ERROR_OUT_OF_MEMORY(110)
      Codeset = 646
          at java.lang.Shutdown.halt0(Native Method)
          at java.lang.Shutdown.halt(Shutdown.java:145)
          - locked <0xd0464db8> (a java.lang.Shutdown$Lock)
          at java.lang.Shutdown.exit(Shutdown.java:219)
          - locked <0xd457c3f8> (a java.lang.Class)
          at java.lang.Runtime.exit(Runtime.java:90)
          at java.lang.System.exit(System.java:868)
          at nsk.jdb.suspend.suspend001a.main(suspend001a.java:21)

      dcubed> At this point, the main thread is calling System.exit() and
      dcubed> something during VM shutdown triggers the backend error.

      ###@###.### 2005-1-25 06:10:58 GMT

      This bug affects the following NSK test:

          nsk/jdb/suspend/suspend001

      ###@###.### 2005-03-11 00:59:32 GMT

        Attachments

          Activity

            People

            • Assignee:
              ohair Kelly Ohair (Inactive)
              Reporter:
              ohair Kelly Ohair (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Imported:
                Indexed: