| Can't Debug Remote java App In Eclipse - Transport Error [message #309181] |
Tue, 17 October 2006 20:56  |
Eclipse User |
|
|
|
Hello:
I am trying to debug a remote Java App with ECLISPE. I have been doing
this for 2 years now and for whatever reason I can no longer do it as of
last week with the error reported below when I try and debug my app.
Any advice would be greatly appreciated.
thanks,
Chris
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=JVMTI_ERROR_INTERNAL(113)
ERROR: transport error 202: connect failed: Connection refused
["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
["debugInit.c",L500]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
|
|
|
| Re: Can't Debug Remote java App In Eclipse - Transport Error [message #309236 is a reply to message #309181] |
Thu, 19 October 2006 12:04  |
| Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Chris wrote:
> Hello:
>
> I am trying to debug a remote Java App with ECLISPE. I have been doing
> this for 2 years now and for whatever reason I can no longer do it as of
> last week with the error reported below when I try and debug my app.
> Any advice would be greatly appreciated.
>
> thanks,
>
> Chris
>
>
>
> FATAL ERROR in native method: JDWP No transports initialized,
> jvmtiError=JVMTI_ERROR_INTERNAL(113)
> ERROR: transport error 202: connect failed: Connection refused
> ["transport.c",L41]
> ERROR: JDWP Transport dt_socket failed to initialize,
> TRANSPORT_INIT(510) ["debugInit.c",L500]
> JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
>
Many remote debug problems are caused by a firewall on one of the
computers that blocks the connection between the debugger and the
running application.
Hope this helps,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.28361 seconds
Home