08-29-2010 10:50 AM
suddenly I got this error if trying to launch the Debugger.
restart Simulator or Eclipse or Windos doesn't helped.
Project-clean-Simulator doesnt help
the Simulator itself works, but the debugger fails:
Failed to connect to remote VM. Connection refused.
java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl
any ideas ?
Solved! Go to Solution.
09-21-2010 06:50 AM
thx to Mark Sohm and others helping and testing so much to find the reason why the Debugger doesnt work.
we failed - all looks good but the Debugger still won't connect to remote VM
so le last step was to create all from scratch:
* create new Parallels VM with Windows 7 64 bit
* install SDK 32 bit
* install Full Eclipse PlugIn and also classic Eclipse + Updatesite
* install new signature keys
and finally it works again
from my POV there's no difference to the prev. installation, but who knows
so I'll watch all my steps carefully - so perhaps if it happens again we'll find the reason
If you're interested: I have described all steps here:
08-29-2010 04:38 PM
I've seen this error when my machine is so loaded down that the simulator takes too much time to connect ot the debug port. Simulators for the newer OS versions take even longer. You can try increasing the timeout values by going to Windows > Options and selecting Debug under Java. I have mine set at 240000 ms (4 minutes).
08-29-2010 05:56 PM
thx for the tip
looked under Eclipse - Preferences - Java . Debug
timeouts for Debug and Launch were 240000
even setting them to 480000 doesnt help
progress shows "Launching... Establishing Connections..." and stops after 10 seconds or so
til yesterday never such a problem, only happens if debugging - normal launch works
08-29-2010 06:09 PM
On older machine, I had to empirically find a ritual and it would work reliably.
Things like starting simulator first, waiting for it to finish loading, and connect
before opening app etc. On new machines it seems more tolerant
08-29-2010 06:18 PM
Launch Simulator - wait - then Debugger: fails
installed a new Simulator outside Eclipse
did Project - BlackBerry clean Simulator
tried again with a small project, no auto-start - same happens
08-29-2010 06:23 PM
switched to another workspace
tried a small rim example project
launching works, debugger fails
I didn't change anything on windows, because I'm using this windows only for developing BB
08-29-2010 06:38 PM
No idea what's happening. The boilerplate question to ask at this point is: has anything changed in your Windows environment since it last worked? (New software, Windows updates, etc. installed?)
08-29-2010 06:52 PM
that's I'm thinking about the whole day:
what could be changed ?
I downloaded and installed some extra Simulators outside Eclipse to test how it works without Eclipse to provide my customer a small environment he can use at an event to demonstryte my apps...
I don't use the debugger many times - mostly I use logging, so I don't remember exactly when I used the debugger last time
think I didn't update windows, I also didn't update Java
all runs inside a VM (Parallels) on top of OSX
so all my 'normal' work runs under OSX - the Windows 7 - Installation inside the VM was only used to develop BB Eclipse apps - all other Eclipse development was done under OSX
will try tomorrow if debugging on the Device works to see if the Debugger itself was working well
thx for helping
09-01-2010 01:42 PM
Do you have any firewall software that could be blocking the connection between Eclipse and the simulator?
A previously running simulator may not have released its port correctly or another application may be using the same port. A restart of Windows may resolve either of these scenarios.
09-01-2010 02:00 PM
there's no Firewall - its my own small LAN
of course I restarted Eclipse,
I restarted Windows
installed brandnew Simulator outside Eclipse and used this one - same happens
tried with/without MDS
swichted to small workspace only containing RIM example apps
same happens - even HelloWorld doesnt work
running Simulator, signing apps, packaging, installing from desktop manager - all works
but Debugger gets Connection TimeOut
if I don't find a solution - you can be sure, I'll have it on my laptop to demonstrate at DevCon to an expert ;-)