 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Mark Searle Guest
|
Posted: Sun Mar 13, 2005 12:57 pm Post subject: VMStartException error |
|
|
Hi,
My JBuilder 2005 has stopped working properly. When I try to debug I get
the following error....
-- Cannot start Java debug process VM --
com.sun.jdi.connect.VMStartException: VM initialization failed for:
C:BorlandJBuilder2005jdk1.4binjavaw -classpath "C:Documents and
SettingsMark
SearlejbprojectHelloclasses;C:BorlandJBuilder2005jdk1.4jrejavawsjavaws.jar;C:BorlandJBuilder2005jdk1.4jrelibcharsets.jar;C:BorlandJBuilder2005jdk1.4jrelibextdnsns.jar;C:BorlandJBuilder2005jdk1.4jrelibextldapsec.jar;C:BorlandJBuilder2005jdk1.4jrelibextlocaledata.jar;C:BorlandJBuilder2005jdk1.4jrelibextsunjce_provider.jar;C:BorlandJBuilder2005jdk1.4jrelibimindicim.jar;C:BorlandJBuilder2005jdk1.4jrelibimthaiim.jar;C:BorlandJBuilder2005jdk1.4jrelibjce.jar;C:BorlandJBuilder2005jdk1.4jrelibjsse.jar;C:BorlandJBuilder2005jdk1.4jrelibplugin.jar;C:BorlandJBuilder2005jdk1.4jrelibrt.jar;C:BorlandJBuilder2005jdk1.4jrelibsunrsasign.jar;C:BorlandJBuilder2005jdk1.4libdt.jar;C:BorlandJBuilder2005jdk1.4libhtmlconverter.jar;C:BorlandJBuilder2005jdk1.4libtools.jar"
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=Rugrat:1138,suspend=y
hello.Untitled1
err:: No such file or directory
Error [2] in connect() call!
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
Its as if the java SDK supplied with Borland has been corrupted. This can't
happen can it? I can run apps in non-debug mode from Jbuilder but cannot
run them in debug mode.
Regards Mark
|
|
| Back to top |
|
 |
Lori M Olson [TeamB] Guest
|
Posted: Mon Mar 14, 2005 3:56 pm Post subject: Re: VMStartException error |
|
|
Mark Searle wrote:
| Quote: | Hi,
My JBuilder 2005 has stopped working properly. When I try to debug I get
the following error....
-- Cannot start Java debug process VM --
com.sun.jdi.connect.VMStartException: VM initialization failed for:
C:BorlandJBuilder2005jdk1.4binjavaw -classpath "C:Documents and
SettingsMark
SearlejbprojectHelloclasses;C:BorlandJBuilder2005jdk1.4jrejavawsjavaws.jar;C:BorlandJBuilder2005jdk1.4jrelibcharsets.jar;C:BorlandJBuilder2005jdk1.4jrelibextdnsns.jar;C:BorlandJBuilder2005jdk1.4jrelibextldapsec.jar;C:BorlandJBuilder2005jdk1.4jrelibextlocaledata.jar;C:BorlandJBuilder2005jdk1.4jrelibextsunjce_provider.jar;C:BorlandJBuilder2005jdk1.4jrelibimindicim.jar;C:BorlandJBuilder2005jdk1.4jrelibimthaiim.jar;C:BorlandJBuilder2005jdk1.4jrelibjce.jar;C:BorlandJBuilder2005jdk1.4jrelibjsse.jar;C:BorlandJBuilder2005jdk1.4jrelibplugin.jar;C:BorlandJBuilder2005jdk1.4jrelibrt.jar;C:BorlandJBuilder2005jdk1.4jrelibsunrsasign.jar;C:BorlandJBuilder2005jdk1.4libdt.jar;C:BorlandJBuilder2005jdk1.4libhtmlconverter.jar;C:BorlandJBuilder2005jdk1.4libtools.jar"
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=Rugrat:1138,suspend=y
hello.Untitled1
err:: No such file or directory
Error [2] in connect() call!
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
Its as if the java SDK supplied with Borland has been corrupted. This can't
happen can it? I can run apps in non-debug mode from Jbuilder but cannot
run them in debug mode.
Regards Mark
|
"Socket transport failed to init."
This sort of thing is generally caused by firewall software blocking the
port over which debugging is trying to communicate.
In your case, that would be port 1138.
"address=Rugrat:1138"
--
Regards,
Lori Olson [TeamB]
------------
Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.
Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html
|
|
| Back to top |
|
 |
yugos Junior Member
Joined: 15 Mar 2006 Posts: 1
|
Posted: Wed Mar 15, 2006 3:11 am Post subject: re:VMStartException error |
|
|
I faced same error and found that the point was port blocking by Virus software. Recent virus software provide not only detecting virus but also port blocking capability, you know.
I used to disable Norton Internet Worm protection in Norton Anti-Virus before booting up JBuilder 2005. |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|