Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8271065 vmTestbase/nsk/jvmti/GetThreadState/thrstat002 still fails with "Wrong thread "thr1" (...) state after SuspendThread"
  3. JDK-8278330

dump stack trace if the jvmti test nsk/jvmti/GetThreadState/thrstat002 is failed with wrong thread state

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 18
    • Fix Version/s: 18
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b28

      Backports

        Description

        The vmTestbase/nsk/jvmti/GetThreadState/thrstat002 test is intermittently failing with the wrong thread state reported. It is most likely because of the unexpected JFR (or NMT) activity.
        This was suggested by David H. :
          We need to dump the stack of the target thread when we find it in the wrong state. It is possible (in the absence of any detailed knowledge about how JFR might operate here) that JFR does cause the thread to go to unexpected code where it can be seen in the wrong state. But we really need to confirm that.

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                sspitsyn Serguei Spitsyn
                Reporter:
                sspitsyn Serguei Spitsyn
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: