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

Test vmTestbase/nsk/jdb/options/connect/connect002/connect002.java failed: connection refused

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: P4 P4
    • tbd
    • 17, 22
    • core-svc
    • x86_64
    • linux

      Main log shows:

      auncher > Starting local debuggee.
      launcher > Start jdb attaching to local debuggee
      debuggee.stderr> Java HotSpot(TM) 64-Bit Server VM warning: Option -Xdebug was deprecated in JDK 22 and will likely be removed in a future release.
      Creating file for jdb stdout stream: ./jdb.stdout
      Creating file for jdb session: ./jdb.session
      Creating file for jdb stderr stream: ./jdb.stderr
      debuggee.stderr> ERROR: transport error 202: bind failed: Address already in use
      debuggee.stderr> ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
      debuggee.stderr> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [/opt/mach5/mesos/work_dir/slaves/cd627e65-f015-4fb1-a1d2-b6c9b8127f98-S75398/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/5203d8ae-c530-430a-aa26-3dd88d31ae56/runs/8d4c964b-573d-4d19-bf37-542195d9f292/workspace/open/src/jdk.jdwp.agent/share/native/libjdwp/debugInit.c:687]
      JdbStderrReader: jdb's stderr is not empty. Check jdb.stderr file
      JdbStderrReader: jdb's stderr is not empty. Check jdb.stderr file
      ...
      # ERROR: Caught unexpected exception: nsk.share.Failure: Launched jdb could not attach to debuggee during 300000 milliseconds.
      The following stacktrace is for failure analysis.
      nsk.share.TestFailure: Caught unexpected exception: nsk.share.Failure: Launched jdb could not attach to debuggee during 300000 milliseconds.
      at nsk.share.Log.logExceptionForFailureAnalysis(Log.java:431)
      at nsk.share.Log.complain(Log.java:402)
      at nsk.share.jdb.JdbTest.failure(JdbTest.java:74)
      at nsk.share.jdb.JdbTest.runTest(JdbTest.java:202)
      at nsk.jdb.options.connect.connect002.connect002.run(connect002.java:81)
      at nsk.jdb.options.connect.connect002.connect002.main(connect002.java:74)
      at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
      at java.base/java.lang.reflect.Method.invoke(Method.java:580)
      at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
      ...


      The jdb.stderr shows:

      java.net.ConnectException: Connection refused
      at java.base/sun.nio.ch.Net.connect0(Native Method)
      at java.base/sun.nio.ch.Net.connect(Net.java:589)
      at java.base/sun.nio.ch.Net.connect(Net.java:578)
      at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:583)
      at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
      at java.base/java.net.Socket.connect(Socket.java:751)
      at jdk.jdi/com.sun.tools.jdi.SocketTransportService.attach(SocketTransportService.java:263)
      at jdk.jdi/com.sun.tools.jdi.GenericAttachingConnector.attach(GenericAttachingConnector.java:119)
      at jdk.jdi/com.sun.tools.jdi.SocketAttachingConnector.attach(SocketAttachingConnector.java:83)
      at jdk.jdi/com.sun.tools.example.debug.tty.VMConnection.attachTarget(VMConnection.java:563)
      at jdk.jdi/com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:369)
      at jdk.jdi/com.sun.tools.example.debug.tty.Env.init(Env.java:63)
      at jdk.jdi/com.sun.tools.example.debug.tty.TTY.main(TTY.java:1176)

      Fatal error:
      Unable to attach to target VM.

            Unassigned Unassigned
            dholmes David Holmes
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: