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

jcmd/TestJcmdSanity.java failed due to "IOException: Bad file descriptor"

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Duplicate
    • Affects Version/s: 13
    • Fix Version/s: None
    • Component/s: core-svc
    • Labels:
    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      linux_ubuntu

      Description

      The following test failed in my jdk13+19 stress testing run:

      sun/tools/jcmd/TestJcmdSanity.java

      Here's a snippet of the log file:

      Java HotSpot(TM) 64-Bit Server VM version 13-internal+0-2019-05-03-1706391.dcubed.null
      JDK 13.0.0
      java.io.IOException: Bad file descriptor
              at jdk.attach/sun.tools.attach.VirtualMachineImpl.connect(Native Method)
              at jdk.attach/sun.tools.attach.VirtualMachineImpl.execute(VirtualMachineImpl.java:160)
              at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.executeCommand(HotSpotVirtualMachine.java:309)
              at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.executeJCmd(HotSpotVirtualMachine.java:291)
              at jdk.jcmd/sun.tools.jcmd.JCmd.executeCommandForPid(JCmd.java:125)
              at jdk.jcmd/sun.tools.jcmd.JCmd.main(JCmd.java:99)

      ----------System.err:(181/9014)----------
      <snip>

      Java HotSpot(TM) 64-Bit Server VM version 13-internal+0-2019-05-03-1706391.dcubed.null
      JDK 13.0.0
      ];
       stderr: [java.io.IOException: Bad file descriptor
              at jdk.attach/sun.tools.attach.VirtualMachineImpl.connect(Native Method)
              at jdk.attach/sun.tools.attach.VirtualMachineImpl.execute(VirtualMachineImpl.java:160)
              at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.executeCommand(HotSpotVirtualMachine.java:309)
              at jdk.attach/sun.tools.attach.HotSpotVirtualMachine.executeJCmd(HotSpotVirtualMachine.java:291)
              at jdk.jcmd/sun.tools.jcmd.JCmd.executeCommandForPid(JCmd.java:125)
              at jdk.jcmd/sun.tools.jcmd.JCmd.main(JCmd.java:99)
      ]
       exitValue = 1

      java.lang.RuntimeException: Expected to get exit value of [0]

              at jdk.test.lib.process.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:430)
              at TestJcmdSanity.testJcmdPidBigScript(TestJcmdSanity.java:120)
              at TestJcmdSanity.main(TestJcmdSanity.java:59)
              at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
              at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.base/java.lang.reflect.Method.invoke(Method.java:567)
              at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
              at java.base/java.lang.Thread.run(Thread.java:830)

      JavaTest Message: Test threw exception: java.lang.RuntimeException: Expected to get exit value of [0]

      JavaTest Message: shutting down test

      STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Expected to get exit value of [0]
      ----------rerun:(35/3722)*----------

      This failure was only seen in 1 of 3 slowdebug runs. It was not
      seen in any of the fastdebug or release runs. I'm marking this
      bug as 'intermittent'.

        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:
                  Resolved: