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

jps test TestJpsSanity.java can intermittently timeout

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 10
    • Fix Version/s: tbd
    • Component/s: core-svc
    • Labels:
    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      solaris_11

      Description

      The following jps test timed out on a recent Solaris X64 'release' bits run:

      sun/tools/jps/TestJpsSanity.java

      Here's a snippet of where the test appears to be timing out:

      "MainThread" #24 prio=5 os_prio=64 tid=0x0000000000b27800 nid=0x50 in Object.wait() [0xffff80ff71dfd000]
         java.lang.Thread.State: WAITING (on object monitor)
              at java.lang.Object.wait(java.base@10-internal/Native Method)
              - waiting on <0x00000004001f4208> (a java.lang.ProcessImpl)
              at java.lang.Object.wait(java.base@10-internal/Object.java:328)
              at java.lang.ProcessImpl.waitFor(java.base@10-internal/ProcessImpl.java:494)
              - waiting to re-lock in wait() <0x00000004001f4208> (a java.lang.ProcessImpl)
              at jdk.testlibrary.ProcessTools.executeProcess(ProcessTools.java:381)
              at jdk.testlibrary.ProcessTools.executeProcess(ProcessTools.java:355)
              at JpsHelper.jps(JpsHelper.java:172)
              at JpsHelper.jps(JpsHelper.java:150)
              at TestJpsSanity.testJpsUnknownHost(TestJpsSanity.java:100)
              at TestJpsSanity.main(TestJpsSanity.java:44)
              at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@10-internal/Native Method)
              at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@10-internal/NativeMethodAccessorImpl.java:62)
              at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@10-internal/DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(java.base@10-internal/Method.java:564)
              at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:115)
              at java.lang.Thread.run(java.base@10-internal/Thread.java:844)

      so the stack trace shows the MainThread is trying to
      run the "jps" cmd.

      Here's the test's output of the "jps" cmds it was trying to run:

      ----------System.out:(24/941)----------
      [/work/shared/bug_hunt/8167108/SMR_base_10/build/solaris-x86_64-normal-server-release/images/jdk/bin/jps -J-XX:+UsePerfData -?]
      usage: jps [-help]
             jps [-q] [-mlvV] [<hostid>]

      Definitions:
          <hostid>: <hostname>[:<port>]

      [/work/shared/bug_hunt/8167108/SMR_base_10/build/solaris-x86_64-normal-server-release/images/jdk/bin/jps -J-XX:+UsePerfData -help]
      usage: jps [-help]
             jps [-q] [-mlvV] [<hostid>]

      Definitions:
          <hostid>: <hostname>[:<port>]

      [/work/shared/bug_hunt/8167108/SMR_base_10/build/solaris-x86_64-normal-server-release/images/jdk/bin/jps -J-XX:+UsePerfData -version]
      illegal argument: -version
      usage: jps [-help]
             jps [-q] [-mlvV] [<hostid>]

      Definitions:
          <hostid>: <hostname>[:<port>]

      [/work/shared/bug_hunt/8167108/SMR_base_10/build/solaris-x86_64-normal-server-release/images/jdk/bin/jps -J-XX:+UsePerfData Oja781nh2ev7vcvbajdg-Sda1-C.invalid]
      Timeout signalled after 360 seconds


      So that last "jps" cmd is the one that timed out.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dcubed Daniel Daugherty
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: