[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.newcomer] Re: "Cannot connect to VM" while Debugging

Kai Hannemann wrote:
Ok, this means that some other process (or another part of Eclipse, theoretically) has created a server socket on that port. Before you start Eclipse, run "netstat -a" and search for something listening on your JPDA port (was it 1453?). That will only tell you if something is listening, but not necessarily what. You could use the TCPView application from Sysinternals to give you a graphical view of what netstat shows, along with the owning process.

Here's what happens when I hit debug in eclipse: javaw opens an (unused) serversocket (the one Kevin Barnes' code would return), listens at this port and keeps listening. So when I hit debug 20 times i get 20 entries in tcpview of javaw listening on different ports.
I made a screenshot for illustration (some ips removed)


http://img482.imageshack.us/img482/852/ports3pw.jpg


Kai,
Seems funny that your system is behaving like this. The code to find a port has been this way in the JDT Debugger for some time now.
Please file a bug against JDT-Debug component.
Thanks
Kevin