| Vista - "Cannot find a free socket for the debugger" [message #257674] |
Thu, 04 December 2008 16:00  |
Eclipse User |
|
|
|
Originally posted by: o.koerber.gmx.de
Hi all,
I have a very strange Problem regarding the debugger within Eclipse
Ganymede. I previously used Eclipse 3.3, but this release still had some
problems displaying the GUI elements. For example half of my projects
within the current workspace were invisible (only when running under Vista).
So I decided to take a look at the newer versions and check if the error
still existed. I installed the eclipse-SDK-3.5M3-win32 Package, and
found out that my display problems had disappeared. But as I tried to
start a debugging session, I got an error message saying "Cannot find a
free socket for the debugger".
Things I tried so far to solve the problem:
- switch of the vista firewall (it wasn't activated, to be precise)
- add a firewall rule for java.exe/javaw.exe/eclipse.exe and reactivated
it (just to be sure it didn't interfere although it was deactivated)
- deactivated my antivirus tool (avira antivir)
- ran eclipse as administrator
- disabled uac
- activated/deactivated wired and wireless network interfaces
- changed priorities of the network interfaces
- used different jvms (1.6 and 1.7)
- created an entirely new workspace
I also tried another Eclipse package, eclipse-java-gaymede-SR1-win32,
based on version 3.4, but with the same problems.
The strange thing though, when I try the debugging using my Eclipse 3.3
installation, there is no problem at all.
Were there any significant changes between 3.3 and 3.4, that could have
caused this problem?
I would be really happy if someone could give me a hint, what the
problem could be, or what I could do to further track down the problem.
Thanks in advance,
Oliver
|
|
|
| SOLVED: Vista - "Cannot find a free socket for the debugger" [message #257690 is a reply to message #257674] |
Fri, 05 December 2008 04:48  |
| Eclipse User |
|
|
|
Originally posted by: o.koerber.gmx.de
Okay, I found out the solution to the problem. Perhaps it could prove as
useful for others too:
The problem is rather strange and I haven't really found out the cause.
But if I enter the path to the java.exe as vm inside my eclipse.ini, it
works. If I instead use javaw.exe, it doesn't. It's strange, but at
least I can use Eclipse again.
See you, thanks for reading.
Oliver
|
|
|
Powered by
FUDForum. Page generated in 0.36366 seconds
Home