java.io.IOException: Bad file number

JDK Bug System | Boris Molodenkov | 5 years ago
  1. Speed up your debug routine!

    Automated exception search integrated into your IDE

  2. 0

    nsk/jdi/AttachingConnector/attach/attach004 failed on linux during 7u25-nightly: http://aurora-ds.ru.oracle.com:9500/runs/188649.JAVASE.NIGHTLY.VM.7u25_Nightly_Baseline.2013-03-20-28/results/ResultDir/attach004/attach004.log Test fails intermittently. Need to investigate is it issue with VM or result of some race condition in test. [2013-03-21T09:38:27.26] # Actual: /bin/bash /export/local/188649.JAVASE.NIGHTLY.VM.7u25_Nightly_Baseline.2013-03-20.linux-i586_vm__client_mixed_nsk.jdi.testlist.runTests/results/ResultDir/attach004//run.sh dt_socket y -waitVMStartEvent [2013-03-21T09:38:27.36] Transport socket is supported at linux-i586 [2013-03-21T09:38:27.36] Transport is supported on this platform, execute test [2013-03-21T09:38:27.36] Start listening debuggee VM: /export/local/common/jdk/baseline/linux-i586/bin/java -client -Xmixed -XX:DefaultMaxRAMFraction=8 -XX:ReservedCodeCacheSize=256M -Xdebug -Xnoagent -agentlib:jdwp=transport=dt_socket,server=y,suspend=y nsk.jdi.AttachingConnector.attach.attach004.attach004t -stressTime 30 -verbose -arch=linux-i586 -waittime=5 -debugee.vmkind=java -transport.address=dynamic -testWorkDir . [2013-03-21T09:38:27.37] Debuggee VM PID: 22109 [2013-03-21T09:38:27.37] Start debugger VM: /export/local/common/jdk/baseline/linux-i586/bin/java -client -Xmixed -XX:DefaultMaxRAMFraction=8 -XX:ReservedCodeCacheSize=256M -Dsun.jvm.hotspot.runtime.VM.disableVersionCheck=1 nsk.jdi.AttachingConnector.attach.attach004.attach004 -debuggeePID 22109 -waitVMStartEvent -stressTime 30 -verbose -arch=linux-i586 -waittime=5 -debugee.vmkind=java -transport.address=dynamic -testWorkDir . [2013-03-21T09:38:27.49] Listening for transport dt_socket at address: 52107 [2013-03-21T09:38:27.62] Connector name=com.sun.jdi.ProcessAttach [2013-03-21T09:38:27.62] description=Attaches to debuggee by process-id (pid) [2013-03-21T09:38:27.62] transport=local [2013-03-21T09:38:37.98] Connection attempt #0 failed: java.io.IOException: Unable to open socket file: target process not responding or HotSpot VM not loaded [2013-03-21T09:38:37.98] java.io.IOException: Unable to open socket file: target process not responding or HotSpot VM not loaded [2013-03-21T09:38:37.98] at com.sun.tools.jdi.ProcessAttachingConnector.attach(ProcessAttachingConnector.java:104) [2013-03-21T09:38:37.98] at nsk.share.jdi.ConnectorTest.tryAttach(ConnectorTest.java:145) [2013-03-21T09:38:37.98] at nsk.jdi.AttachingConnector.attach.attach004.attach004.doTest(attach004.java:96) [2013-03-21T09:38:37.98] at nsk.share.jdi.ConnectorTest.runIt(ConnectorTest.java:109) [2013-03-21T09:38:37.98] at nsk.jdi.AttachingConnector.attach.attach004.attach004.run(attach004.java:44) [2013-03-21T09:38:37.98] at nsk.jdi.AttachingConnector.attach.attach004.attach004.main(attach004.java:40) ... [2013-03-21T09:56:13.55] Connection attempt #74 failed: java.io.IOException: Unable to open socket file: target process not responding or HotSpot VM not loaded [2013-03-21T09:56:13.55] java.io.IOException: Unable to open socket file: target process not responding or HotSpot VM not loaded [2013-03-21T09:56:13.55] at com.sun.tools.jdi.ProcessAttachingConnector.attach(ProcessAttachingConnector.java:104) [2013-03-21T09:56:13.55] at nsk.share.jdi.ConnectorTest.tryAttach(ConnectorTest.java:145) [2013-03-21T09:56:13.55] at nsk.jdi.AttachingConnector.attach.attach004.attach004.doTest(attach004.java:96) [2013-03-21T09:56:13.55] at nsk.share.jdi.ConnectorTest.runIt(ConnectorTest.java:109) [2013-03-21T09:56:13.55] at nsk.jdi.AttachingConnector.attach.attach004.attach004.run(attach004.java:44) [2013-03-21T09:56:13.55] at nsk.jdi.AttachingConnector.attach.attach004.attach004.main(attach004.java:40) [2013-03-21T09:56:17.55] # ERROR: FAILURE: all attempts to connect to the debuggee VM failed [2013-03-21T09:56:17.55] # ERROR: Unable to attach the debugee VM [2013-03-21T09:56:17.55] Unexpected exception: java.lang.NullPointerException [2013-03-21T09:56:17.55] java.lang.NullPointerException [2013-03-21T09:56:17.55] at nsk.jdi.AttachingConnector.attach.attach004.attach004.doTest(attach004.java:101) [2013-03-21T09:56:17.55] at nsk.share.jdi.ConnectorTest.runIt(ConnectorTest.java:109) [2013-03-21T09:56:17.55] at nsk.jdi.AttachingConnector.attach.attach004.attach004.run(attach004.java:44) [2013-03-21T09:56:17.55] at nsk.jdi.AttachingConnector.attach.attach004.attach004.main(attach004.java:40)

    JDK Bug System | 4 years ago | Filipp Zhinkin
    java.io.IOException: Unable to open socket file: target process not responding or HotSpot VM not loaded
  3. 0

    java.io.IOException: Stream closed

    Oracle Community | 5 years ago | 651737
    java.io.IOException: Bad file number]: : java.io.IOException: Bad file number

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      Bad file number

      at com.sun.tools.jdi.ProcessAttachingConnector.attach()
    2. Java Tools
      ProcessAttachingConnector.attach
      1. com.sun.tools.jdi.ProcessAttachingConnector.attach(ProcessAttachingConnector.java:104)
      1 frame
    3. nsk.share.jdi
      ConnectorTest.tryAttach
      1. nsk.share.jdi.ConnectorTest.tryAttach(ConnectorTest.java:145)
      1 frame
    4. nsk.jdi.AttachingConnector
      attach004.doTest
      1. nsk.jdi.AttachingConnector.attach.attach004.attach004.doTest(attach004.java:96)
      1 frame
    5. nsk.share.jdi
      ConnectorTest.runIt
      1. nsk.share.jdi.ConnectorTest.runIt(ConnectorTest.java:109)
      1 frame
    6. nsk.jdi.AttachingConnector
      attach004.main
      1. nsk.jdi.AttachingConnector.attach.attach004.attach004.run(attach004.java:44)
      2. nsk.jdi.AttachingConnector.attach.attach004.attach004.main(attach004.java:40)
      2 frames