Eclipse Community Forums: Java Development Tools (JDT) » Debugging a remote Java application with Eclipse as the server (Socket listen)

Home » Language IDEs » Java Development Tools (JDT) » Debugging a remote Java application with Eclipse as the server (Socket listen)

Show: Today's Messages :: Show Polls :: Message Navigator

Debugging a remote Java application with Eclipse as the server (Socket listen) [message #698677]

Wed, 20 July 2011 00:12

ranjitiyer

Messages: 1
Registered: July 2011

Junior Member

I am trying to debug a remote Java application from Eclipse, with Eclipse acting as the Server as opposed acting as a Client to the remote application. I launch the remote application with the following JVM options where 'server=n' will cause the remote application to connect back to Eclipse (Socket Listen) instead of Eclipse connecting to the remote app (Socket Attach).

-Xdebug -Xrunjdwp:transport=dt_socket,server=n,suspend=n,address=8000

Finally, I configure Eclipse to listen on a port and then launch the remote app. The app connects to Eclipse and my breakpoints are hit. However, when I launch a second instance of the remote app with the above JVM options, the app fails with the following error indicating it was unable to connect to Eclipse.

ERROR: transport error 202: connect failed: Connection refused

Is there a known issue in Eclipses' remote debugging that limits only one remote app to connect to it at a given time?

Thanks for any insights.

Report message to a moderator

Re: Debugging a remote Java application with Eclipse as the server (Socket listen) [message #698698 is a reply to message #698677]

Wed, 20 July 2011 02:06

David Wegener

Messages: 1445
Registered: July 2009

Senior Member

On 07/19/2011 07:12 PM, forums-noreply@eclipse.org wrote:
> I am trying to debug a remote Java application from Eclipse, with
> Eclipse acting as the Server as opposed acting as a Client to the remote
> application. I launch the remote application with the following JVM
> options where 'server=n' will cause the remote application to connect
> back to Eclipse (Socket Listen) instead of Eclipse connecting to the
> remote app (Socket Attach).
>
> -Xdebug -Xrunjdwp:transport=dt_socket,server=n,suspend=n,address=8000
>
> Finally, I configure Eclipse to listen on a port and then launch the
> remote app. The app connects to Eclipse and my breakpoints are hit.
> However, when I launch a second instance of the remote app with the
> above JVM options, the app fails with the following error indicating it
> was unable to connect to Eclipse.
>
> ERROR: transport error 202: connect failed: Connection refused
>
> Is there a known issue in Eclipses' remote debugging that limits only
> one remote app to connect to it at a given time?
>
You already have a connection active on port 8000. You can't have two
connections to the same port number. You need to specify a different
port for the second connection.

> Thanks for any insights.

Report message to a moderator

Previous Topic:	JDI/JDWP trace
Next Topic:	Java Model Status "Invalid name specified" exception - Possible bug

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 19:51:42 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter