| Unable to connect to VM for debug [message #79518] |
Wed, 23 July 2003 22:02  |
Eclipse User |
|
|
|
Originally posted by: runningoutofword.netscape.net
Hi -
Has any one seen this problem when launching a runtime debug workbench??
(this is displayed at the Console)
err:: No such file or directory
FATAL ERROR in native method: No transports initialized
Error [2] in connect() call!
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
I have re-booted, re-started the workbench and the runtime
workbench.. - but that doesn't seem to help. The other problem
is that.. I am not aware of anything different that I did recently
to my machine that is causing all my existing workspaces to just
fail like that. (except that I was doing more NLS work...)
I am using Eclipse 3.0M2 build, with runtime target of Eclipse 3.0M2
build (with some local plugin added). Both JVMs that I am using
are 1.3.1_08 . I've tested this on 1.4.1_02 but the problem still
appears.. The thing is - runtime workbench will run correctly
without debug...
Anyhelp would be much appreciated.
Thanks.
Ying
(this is the stuff that appears in the .log file)
java.version=1.3.1_08
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -data F:\WorkSpaces\0716_M3 -install
file:F:/ECLIPSE_SDK_3.0M2_WIN32/eclipse/
!ENTRY org.eclipse.debug.ui 4 120 Jul 23, 2003 15:17:21.552
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[120]: java.net.SocketException:
socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.accept( SocketTransportImpl.java:84)
at
org.eclipse.jdi.internal.connect.SocketListeningConnectorImp l.accept(SocketListeningConnectorImpl.java:123)
at
org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec tRunnable.run(StandardVMDebugger.java:77)
at java.lang.Thread.run(Thread.java:479)
!ENTRY org.eclipse.jdt.launching 4 120 Jul 23, 2003 15:17:21.552
!MESSAGE Cannot connect to VM
!STACK 0
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.accept( SocketTransportImpl.java:84)
at
org.eclipse.jdi.internal.connect.SocketListeningConnectorImp l.accept(SocketListeningConnectorImpl.java:123)
at
org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec tRunnable.run(StandardVMDebugger.java:77)
at java.lang.Thread.run(Thread.java:479)
!ENTRY org.eclipse.debug.ui 4 120 Jul 23, 2003 16:47:16.589
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[120]: java.net.SocketException:
socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.accept( SocketTransportImpl.java:84)
at
org.eclipse.jdi.internal.connect.SocketListeningConnectorImp l.accept(SocketListeningConnectorImpl.java:123)
at
org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec tRunnable.run(StandardVMDebugger.java:77)
at java.lang.Thread.run(Thread.java:479)
!ENTRY org.eclipse.jdt.launching 4 120 Jul 23, 2003 16:47:16.589
!MESSAGE Cannot connect to VM
!STACK 0
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.accept( SocketTransportImpl.java:84)
at
org.eclipse.jdi.internal.connect.SocketListeningConnectorImp l.accept(SocketListeningConnectorImpl.java:123)
at
org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec tRunnable.run(StandardVMDebugger.java:77)
at java.lang.Thread.run(Thread.java:479)
!ENTRY org.eclipse.debug.ui 4 120 Jul 23, 2003 17:27:39.49
!MESSAGE Error logged from Debug UI:
!STACK 1
org.eclipse.core.runtime.CoreException[120]: java.net.SocketException:
socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.accept( SocketTransportImpl.java:84)
at
org.eclipse.jdi.internal.connect.SocketListeningConnectorImp l.accept(SocketListeningConnectorImpl.java:123)
at
org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec tRunnable.run(StandardVMDebugger.java:77)
at java.lang.Thread.run(Thread.java:479)
!ENTRY org.eclipse.jdt.launching 4 120 Jul 23, 2003 17:27:39.49
!MESSAGE Cannot connect to VM
!STACK 0
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:463)
at java.net.ServerSocket.implAccept(ServerSocket.java:238)
at java.net.ServerSocket.accept(ServerSocket.java:217)
at
org.eclipse.jdi.internal.connect.SocketTransportImpl.accept( SocketTransportImpl.java:84)
at
org.eclipse.jdi.internal.connect.SocketListeningConnectorImp l.accept(SocketListeningConnectorImpl.java:123)
at
org.eclipse.jdt.internal.launching.StandardVMDebugger$Connec tRunnable.run(StandardVMDebugger.java:77)
at java.lang.Thread.run(Thread.java:479)
|
|
|
|
| Re: Unable to connect to VM for debug [message #79912 is a reply to message #79776] |
Thu, 24 July 2003 20:35  |
| Eclipse User |
|
|
|
Originally posted by: runningoutofword.netscape.net
I am getting the same error message as the problem report.
But - since the problem was originated in late 2001 - and it is
mid 2003 now.. I would've suppose that the patch that you mentioned
at the bug report is rolled up to the most recent Eclipse 3.0M2 build.
(let me know otherwise - I can download that plugin that you've
mentioned in the bug report and try it). I also tried runing this
without network connection, and it fails with the same message.
I am suspecting a network problem on my machine - as other people
in my team does not run into the same problem. unfortunately,
I was not aware of any changes to the network. Is there something
that I can do to get more information about this? Are there
anything that I should be checking that I am missing?
Thanks.
Ying
Darin Wright wrote:
> See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=6437
>
> Darin
>
>
|
|
|
| Re: Unable to connect to VM for debug - solved... [message #80193 is a reply to message #79776] |
Fri, 25 July 2003 14:11 |
| Eclipse User |
|
|
|
Originally posted by: runningoutofword.netscape.net
Thanks for the help.
I wrote a very simple C/S program to test things out -
to make sure that it is not Eclipse. My client wasn't
able to create a new Socket, on the port that I've just
created on my server program. Tested the same program on
a different machine - and the program ran correctly.
So - at least I know that it was my machine screwing up.
I was going to wipe out my OS and re-install but realized that
my firewall might be preventing my network connection. After
disableing it - things work! Now on to figure out which rule
that is blocking socket creation.
Thanks again!
Ying
Darin Wright wrote:
> See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=6437
>
> Darin
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04004 seconds
] 
Search
Help
Register
Login
Home
