Debugging engine not connected to IDE

[rioba]

When I try to use the debugger and click on the Step Over button, most of the time the arrow indicating the active line of code dissapears, the debugger stops and the MacOS X spinning wheel appears, often followed by a message: debugging engine not connected to IDE (or maybe IDE not connected to debugging engine, I am not sure).

The strange think is that this may or may not happen at the same breakpoint, but I can't understand why. Any suggestion?

[jcompagner]

do you have the variables view then visible?

If you close the variables view do you still have that?
I fixed already some problems in that area where some variables would kill the debugger like that.

[rioba]

I always have the variable view open. I will try closing it and see what happens.

[rioba]

Yes, closing the variables view solves the freezing but now I can't evaluate what's happening. It is a sort of Catch 22 situation.

I also noticed this message when I try to force quit Servoy Eclipse: "rebuilding workspace", and a progress bar appears in the lower right corner of the Eclipse window

[jcompagner]

The stability in the debugging area (with the variables view) is greatly improved for 4.0.1

[Bounce]

Hi all,

I am new to servoy but i am already quite excited by the features i have seen.
I have installed servoy successfully on my Ubuntu box and i have managed to create a solution that connects to a mysql database.

The problem is every time i want to launch the smart client it works but in the background it is trying to "launch globals.js" and that hangs at 78%. After a while it comes back with an error "Debugging engine not connected to IDE".
The other issue (which might be linked to the first) is that i can't start a webclient. Whenever i click on that button it seems to load something but in the end nothing happens.

Is servoy even compatible with Ubuntu?

Thanks for your help,
Regards,
Bounce

[jcompagner]

dont you see anything else in the log (servoy_log.txt or .log in workspace dir)? (except that debugging engine not connected, because thats just a result of)

it could be that some port is blocked i think we try to open something like 10000 where the debugger then wants to connect to.

[Bounce]

Thanks for the reply,

I checked but i see no log files in my servoy_workspace directory. I only have a resource folder and a folder for my solution.
I haven't yet checked to see if port 10000 is closed though knowing Ubuntu i should think that it is.
I will check this and get back to you.

Cheers,
B.

[jcompagner]

there has to me a .metadata dir
please look carefully because it starts with a . so it is invisible be default for many things.

[Bounce]

All good thanks !

1) The files were hidden ... duh
2) I opened udp port 10 000 and the problem is solved !

For anyone who needs to do this on Ubuntu : sudo iptables -I INPUT -p udp --dport 10000 -j ACCEPT
Thanks for your help.

[Gary R. Schaecher]

We are having continuing problems when using the debugger in both 4.0.1 and 4.1beta1 where we get "Debugging engine not connect to IDE" appears. Really is frustrating when trying to debug code. Hope it gets stable sooner rather than later.

[full_noize]

I am running a Windows 2003 server box and keep getting this 'Debugging engine not connected to IDE'. I have opened port 10000 (both UDP and TCP) with no success. Is there any thing else that anyone out may have tried with this issue that has been successful?

[jcompagner]

with the current release of servoy 4.1.x there is no need to open a port.
It will try find a free port and use that one.

I guess on windows 2003 server the process isnt allowed to open up any ports?
Does the admin pages work if you have started te developer?

[full_noize]

Hi Johan,

I got it working, tried a few things that didn't seem to work (shut down ipnat.sys, opened the udp and tcp 10000 but as you say this shouldn't make a difference, stopped and started the remote access service) until I restarted the server and Servoy so I am not exactly sure what did it, but Win2003 can be a law unto itself sometimes...

I have been following your tutorial on debugging Servoy 4.x and I don't have the Script debug console available as an option... Am I missing something or is this an 'issue'? Thanks for your help Johan, your tutorial is very good by the way.

[jcompagner]

Script Debug Console is replaced by the Interactive Console in 4.1