Can't debugg using java 1.5 Beta 1

Hi,

I am trying to debug my application using Java 1.5 beta 1 but I get the following error message.


Any ideas what the problem could be?

Thanks
-Hinke

5 comments
Comment actions Permalink

Hi,

Unfortunately, VM debugging interface was significantly changed in 1.5
so that it is not possible right now to launch debugging with Pallada
and 1.5 VM. Please, post the request to tracker.

Henrik Engert wrote:

Hi,

I am trying to debug my application using Java 1.5 beta 1 but I get the following error message.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) > Warning: classic VM not supported; client VM will be used > ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_LOAD(509) ["debugInit.c",L476] > JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized]]>

Any ideas what the problem could be?

Thanks
-Hinke



--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

Thanks for the reply. I reported it to Tracker. I'll switch back to Java 1.4 then.

-Henrik

0
Comment actions Permalink

I was able to get this working by updating my path.

The key is to have the JDK 1.5 beta JRE bin directory
listed in your path. (make sure it comes before any
other JREs).

For some reason the DLLS needed for debugging do not
show up in the SDK bin directory, only the JRE bin.

I now have this working under build 2026.

0
Comment actions Permalink

Has anyone made any ground on this? I am running jdk 1.5.0_04 and am still getting the same problem. I have tried setting my paths as the previous thread states, but no luck. I am still getting:

ERROR: transport error 202: connect failed: Connection refused ["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L497]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)


Any help is appreciated.

Thanks,
-J

0
Comment actions Permalink

Any new information available on this topic?

I am also seeing this exception but can't figure out why and what to do against it.

0

Please sign in to leave a comment.