19 !ENTRY org.python.pydev.debug 4 4 2008-05-22 06:25:44.129
20 !MESSAGE Timed out after 100.0 seconds while waiting for python script to connect.
21 !STACK 0
22 java.net.SocketTimeoutException: Accept timed out
23 at gnu.java.net.PlainSocketImpl.accept(libgcj.so.90)
24 at gnu.java.net.PlainSocketImpl.accept(libgcj.so.90)
25 at java.net.ServerSocket.implAccept(libgcj.so.90)
26 at java.net.ServerSocket.accept(libgcj.so.90)
27 at org.python.pydev.debug.model.remote.ListenConnector.run(ListenConnector.java:40)
28 at java.lang.Thread.run(libgcj.so.90)
I read some similar questions, but I don't know how to do.
I use debian testing ,python 2.5 ,pydev 1.3.17.
I don't know why Timeout? I don't use firewall and eth0 is OK.
Thanks~
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just had the same problem. It turns out the debugger tries to connect to localhost - if localhost does not resolve properly, the debugger will timeout and not give a terribly useful error. To correct the problem add "localhost 127.0.0.1" to your /etc/hosts file.
Hope this help.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
19 !ENTRY org.python.pydev.debug 4 4 2008-05-22 06:25:44.129
20 !MESSAGE Timed out after 100.0 seconds while waiting for python script to connect.
21 !STACK 0
22 java.net.SocketTimeoutException: Accept timed out
23 at gnu.java.net.PlainSocketImpl.accept(libgcj.so.90)
24 at gnu.java.net.PlainSocketImpl.accept(libgcj.so.90)
25 at java.net.ServerSocket.implAccept(libgcj.so.90)
26 at java.net.ServerSocket.accept(libgcj.so.90)
27 at org.python.pydev.debug.model.remote.ListenConnector.run(ListenConnector.java:40)
28 at java.lang.Thread.run(libgcj.so.90)
I read some similar questions, but I don't know how to do.
I use debian testing ,python 2.5 ,pydev 1.3.17.
I don't know why Timeout? I don't use firewall and eth0 is OK.
Thanks~
Hi,
Well, aside from the firewall and eth0, the most common problem is gcj... try using a different vm and see if the error persists.
Cheers,
Fabio
I just had the same problem. It turns out the debugger tries to connect to localhost - if localhost does not resolve properly, the debugger will timeout and not give a terribly useful error. To correct the problem add "localhost 127.0.0.1" to your /etc/hosts file.
Hope this help.
Brian