Cannot Start Java Debug Process VM
HI,
I'm not able to debug even a hello World using JBuilder2005. I can run it and build it successfully but can't debug. The following error message displayed while trying to debug
-- Cannot start Java debug process VM --
com.sun.jdi.connect.VMStartException: VM initialization failed for: "E:\Program Files\Java\jdk1.5.0_01\bin\javaw" -classpath "F:\CODE\Try\classes;E:\Program Files\Java\jdk1.5.0_01\demo\jfc\CodePointIM\CodePointIM.jar;E:\Program Files\Java\jdk1.5.0_01\demo\jfc\Java2D\Java2Demo.jar;E:\Program Files\Java\jdk1.5.0_01\demo\plugin\jfc\CodePointIM\CodePointIM.jar;E:\Program Files\Java\jdk1.5.0_01\demo\plugin\jfc\Java2D\Java2Demo.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\charsets.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\deploy.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\ext\dnsns.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\ext\localedata.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\ext\sunjce_provider.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\ext\sunpkcs11.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\im\indicim.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\im\thaiim.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\javaws.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\jce.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\jsse.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\plugin.jar;E:\Program Files\Java\jdk1.5.0_01\jre\lib\rt.jar;E:\Program Files\Java\jdk1.5.0_01\lib\dt.jar;E:\Program Files\Java\jdk1.5.0_01\lib\htmlconverter.jar;E:\Program Files\Java\jdk1.5.0_01\lib\jconsole.jar;E:\Program Files\Java\jdk1.5.0_01\lib\tools.jar;E:\Program Files\Java\jdk1.5.0_01\sample\jnlp\servlet\jardiff.jar;E:\Program Files\Java\jdk1.5.0_01\sample\jnlp\servlet\jnlp-servlet.jar;E:\Program Files\Java\jdk1.5.0_01\sample\jnlp\servlet\jnlp.jar" -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=Tiramisu:1645,suspend=y Hello
I've tried with 1.4.2 04 as well as 1.4.2 06 but of no use.
I'm not able to debug my existing projects even with Eclipse.
I created a new HelloWorld with Eclipse and it is getting debugged but my existing projects are giving the following exception:
Cannot connect to VM
java.net.SocketException: socket closed
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(Unknown Source)
java.net.ServerSocket.implAccept(Unknown Source)
java.net.ServerSocket.accept(Unknown Source)
org.eclipse.jdi.internal.connect.SocketTransportImpl.accept(SocketTransportImpl.java:87)
org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.accept(SocketListeningConnectorImpl.java:124)
org.eclipse.jdt.internal.launching.StandardVMDebugger$ConnectRunnable.run(StandardVMDebugger.java:78)
java.lang.Thread.run(Unknown Source)
I've tried reinstalling everything except windows but I failed to debug. I've used many method I found in other threads like copying dt_socket and dt_shmem.dll to system dir or adding jre\bin or jdk\bin to path but nothing helped.
Is there any other solution than reinstalling widows itself which I'm not at all intersted.
Thanks
[3187 byte] By [
Dev.Qa] at [2007-10-1 5:11:45]
hey man, i have the same problem, just from one day to another, i can't debug anymore, don't know what happened, i checked it with another machine from a collague and everything has the same setting, i just don't understand it
I have the same problem. One day it worked and one day it didn't. I've uninstalled and reinstalled JBuilder but it didn't help. Help!
Hi,
I have just had the very same thing happen to my machine.I have Jbuilder 2005. The only thing I have done to my machine since programming yesterday was to install a Creative Camera and listen to Radiohead.Do you think my computer is depressed? Does anyone have a solution yet?
Regards Mark
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=Tiramisu:1645,suspend=y Hello
should be
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y ,address=Tiramisu:1645,suspend=y Hello
Then,
I suggest to use Netbeans4.0 to debug java program.
There're really cool debug features in Netbeans4.0 (http://www.netbeans.org)
> Hi,
>
> I have just had the very same thing happen to my
> machine.I have Jbuilder 2005. The only thing I
> have done to my machine since programming yesterday
> was to install a Creative Camera and listen to
> Radiohead.Do you think my computer is depressed?
> Does anyone have a solution yet?
>
It worked yesterday.
You installed something.
Today it doesn't work.
Wild guess - what you installed changed something.
I've got the same problem after in stalled on my computer (runs WindowsXP, SP2) the jdk 1.5...When I try to debug the code from Eclipse 3.1, I have the following :
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",L497]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
Would be perfect if any one can help to solve this problem...
I also tried to reinstall the jdk, replacing it with j2se1.4.2_07 that worked just fine before on this same system, but nothing helped...
Thanks!
The funny thing is, if you try to start the program in debug mode multiple times (number varies) it works fine.
C:\jakarta-tomcat\bin>catalina jpda run
Using CATALINA_BASE:C:\jakarta-tomcat
Using CATALINA_HOME:C:\jakarta-tomcat
Using CATALINA_TMPDIR: C:\jakarta-tomcat\temp
Using JAVA_HOME:C:\jdk1.5.0
ERROR: transport error 202: listen failed: Invalid argument ["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
C:\jakarta-tomcat\bin>catalina jpda run
Using CATALINA_BASE:C:\jakarta-tomcat
Using CATALINA_HOME:C:\jakarta-tomcat
Using CATALINA_TMPDIR: C:\jakarta-tomcat\temp
Using JAVA_HOME:C:\jdk1.5.0
ERROR: transport error 202: listen failed: Invalid argument ["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
C:\jakarta-tomcat\bin>catalina jpda run
Using CATALINA_BASE:C:\jakarta-tomcat
Using CATALINA_HOME:C:\jakarta-tomcat
Using CATALINA_TMPDIR: C:\jakarta-tomcat\temp
Using JAVA_HOME:C:\jdk1.5.0
ERROR: transport error 202: listen failed: Invalid argument ["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
C:\jakarta-tomcat\bin>catalina jpda run
Using CATALINA_BASE:C:\jakarta-tomcat
Using CATALINA_HOME:C:\jakarta-tomcat
Using CATALINA_TMPDIR: C:\jakarta-tomcat\temp
Using JAVA_HOME:C:\jdk1.5.0
Listening for transport dt_socket at address: 8888
the new jbuilder will try to bind to a host, and if that host doesn't resolve to your localhost, then you need to add it in /etc/hosts or /windows/system32/drivers/etc/hosts
for example, jbuilder will do this
-Xrunjdwp:transport=dt_socket,address=fedora2.domain.com:33195,suspend=y
in this case, fedora2.domain.com must resolve to 127.0.0.1 or your machines IP
I just had the same problem. It took a while until I found out that my firewall blocked JBuilder. Now it works fine. :)
In my case the problem was not a firewall. I had some environment variable, including "path" defined in the debugging configuration I was using, and had the "Replace native environment with specified environment" radio button selected. That was the cause of the problem.
I Switched the button to "Append Environment to native environment" and it started working.
Hope this helps,
Roberto
i was the same problem, i just change the jdk in the runtime configuration from 1.4 to 1.5 and all works fine...Hope this helps, Giovanny Gutierrez
Hi,
catalina.bat uses defult values for JPDA_TRANSPORT and JPDA_ADDRESS env vars.
Add the following lines to the begining of catalina.bat
SET JPDA_TRANSPORT=dt_socket
SET JPDA_ADDRESS=8000
After this jvm will be listen on 0.0.0.0:8000.
I use jdk1.4.2_08.
Regards,
Istv醤
Same for me - it was definitely ZoneAlarm that blocked JBuilder.
Problem was, it did not complain either - just dropped it.
ZA running - JB just won't start the debug process
Shut down ZA - JB starts the debug ok
Restart ZA - JB throws the exception again
BTW - you want to check the hosts file (winnt/system32/drivers/etc) - it does not matter whether it's set to localhost or to the actual IP of your NIC (I have it on 192.168.1.50) but JB definitely tries to connect to the debug server (on port 3250 on mine) using the name of the machine, not the IP address - so it must resolve it somewhere.
I suggest you check out the value in "server=xxxxx" and try and do a 'ping xxxxx' using a DOS prompt - if it pings. then you're in business.
Hope this helps, cheers
Marco.
I had the same problem. I was able to run but not debug. None of the things mentioned help. I didnt know how to modify following string(so I didnt try one of the mentioned methods above):
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=lasvegas:1085,suspend=y de.rac.overture.SearchTool
But I found another workaround. I changed my computers name(right click on my computer->properties->computer) from lasvegas to localhost. After I restarted my computer it worked!!!
