TestJcmd.java 5 seconds can be not enough to start a container

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: 8
    • Component/s: hotspot
    • linux

      TestJcmd.java gives only 5 second for container to be launched. But is it's often not enough.
      The test fails with the following call call stack

      java.util.concurrent.TimeoutException
              at com.oracle.java.testlibrary.ProcessTools.startProcess(ProcessTools.java:151)
              at TestJcmd.startObservedContainer(TestJcmd.java:183)
              at TestJcmd.main(TestJcmd.java:79)


      We might need to increase the timeout (.e.g. to 15s).

            Assignee:
            Ivan Bereziuk
            Reporter:
            Ivan Bereziuk
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: