Topic
  • 2 replies
  • Latest Post - ‏2002-08-05T14:31:16Z by SystemAdmin
SystemAdmin
SystemAdmin
9394 Posts

Pinned topic debugging connection to a remote J9 fails in Eclipse 2.0

‏2002-08-02T14:52:16Z |
I tried to open a remote debug session to a j9 1.5 (running once
on localhost and once truely remote).
Both times the remote j9 is waiting for the connect.

In Eclipse I get an error that the connection failed.

Eclipse shows the following error in the log:

!ENTRY org.eclipse.debug.ui 4 120 Aug 02, 2002 01:42:31.907
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException113: java.io.IOException: EOF
encoutered during handshake
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.PerformHandshake(SocketTransportImpl.java:138)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.attach(SocketTransportImpl.java:42)
at
org.eclipse.jdi.internal.connect.SocketAttachingConnectorImpl.attach(SocketAttachingConnectorImpl.java:95)
at
org.eclipse.jdt.internal.launching.SocketAttachConnector.connect(SocketAttachConnector.java:113)
at
org.eclipse.jdt.internal.launching.JavaRemoteApplicationLaunchConfigurationDelegate.launch(JavaRemoteApplicationLaunchConfigurationDelegate.java:59)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:136)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog$10.run(LaunchConfigurationDialog.java:2299)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:98)
I have tried it with a jdk 1.4 as default jre
and with j9 after installing org.eclipse.jdt.launching.j9_20020625.zip.

It makes no difference

Any ideas what goes wrong ?

Regards,
Stefan
Updated on 2002-08-05T14:31:16Z at 2002-08-05T14:31:16Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: debugging connection to a remote J9 fails in Eclipse 2.0

    ‏2002-08-02T16:48:27Z  
    "Stefan Bittner" <bittner@3Soft.de> wrote in message
    news:3D4A9CA0.9070301@3Soft.de...
    > I tried to open a remote debug session to a j9 1.5 (running once
    > on localhost and once truely remote).
    > Both times the remote j9 is waiting for the connect.
    >
    > In Eclipse I get an error that the connection failed.
    >
    > Eclipse shows the following error in the log:
    >
    Stefan,

    Did you also start the j9proxy?

    J9 does not directly understand the JDWP. Instead, it speaks a simpler
    protocol to j9proxy, which acts as a proxy between the VM and the
    debugger. This offloads much of the complex work of debugging from the
    VM to a seperate program.

    /peter
  • SystemAdmin
    SystemAdmin
    9394 Posts

    Re: debugging connection to a remote J9 fails in Eclipse 2.0

    ‏2002-08-05T14:31:16Z  
    "Stefan Bittner" <bittner@3Soft.de> wrote in message
    news:3D4A9CA0.9070301@3Soft.de...
    > I tried to open a remote debug session to a j9 1.5 (running once
    > on localhost and once truely remote).
    > Both times the remote j9 is waiting for the connect.
    >
    > In Eclipse I get an error that the connection failed.
    >
    > Eclipse shows the following error in the log:
    >
    Stefan,

    Did you also start the j9proxy?

    J9 does not directly understand the JDWP. Instead, it speaks a simpler
    protocol to j9proxy, which acts as a proxy between the VM and the
    debugger. This offloads much of the complex work of debugging from the
    VM to a seperate program.

    /peter
    Peter Burka wrote:
    > "Stefan Bittner" <bittner@3Soft.de> wrote in message
    > news:3D4A9CA0.9070301@3Soft.de...
    >
    >>I tried to open a remote debug session to a j9 1.5 (running once
    >>on localhost and once truely remote).
    >>Both times the remote j9 is waiting for the connect.
    >>
    >>In Eclipse I get an error that the connection failed.
    >>
    >>Eclipse shows the following error in the log:
    >>
    >
    >
    >
    > Stefan,
    >
    > Did you also start the j9proxy?
    >
    > J9 does not directly understand the JDWP. Instead, it speaks a simpler
    > protocol to j9proxy, which acts as a proxy between the VM and the
    > debugger. This offloads much of the complex work of debugging from the
    > VM to a seperate program.
    >
    > /peter
    >
    >
    >

    No, I didn't. That was it. Thank You

    -Stefan