During a method execution, I get this in the console:
null
Stack trace:
#0 file:/C:/rf/servoy_workspace/ocifam/forms/ocifam_srl.js [63]
#1 file:/C:/rf/servoy_workspace/ocifam/forms/ocifam_srl.js [127]
I would have assumed, this is a syntax error on these lines, but the pb is random though these lines are in a loop which runs many times.
The error log which goes with it is:
message: Internal error logged from DLTKDebugPlugin: null
stack trace:
org.eclipse.dltk.dbgp.exceptions.DbgpTimeoutException
at org.eclipse.dltk.dbgp.internal.commands.DbgpDebuggingEngineCommunicator.communicate(DbgpDebuggingEngineCommunicator.java:88)
at org.eclipse.dltk.dbgp.DbgpBaseCommands.communicate(DbgpBaseCommands.java:43)
at org.eclipse.dltk.dbgp.internal.commands.DbgpContinuationCommands.execCommand(DbgpContinuationCommands.java:35)
at org.eclipse.dltk.dbgp.internal.commands.DbgpContinuationCommands.run(DbgpContinuationCommands.java:43)
at org.eclipse.dltk.dbgp.internal.commands.DbgpCoreCommands.run(DbgpCoreCommands.java:137)
at org.eclipse.dltk.internal.debug.core.model.operations.DbgpResumeOperation.process(DbgpResumeOperation.java:23)
at org.eclipse.dltk.internal.debug.core.model.operations.DbgpOperation$1.run(DbgpOperation.java:64)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
no need to tell that this kind of reporting does not talk to me.
what is your preference value you have in
Preferences->Dynamic Languages → Debug
and then the response timeout value?
That one should be on 0
was on 3600s (1 hour), so I set it to 0 (infinite I guess)
still times out after a while (eclipse been restarted of course)
here is what I get in the console:
…
write count=20600
write count=20700
write count=20800
null
Stack trace:
#0 file:/C:/rf/servoy_workspace/ocifam/forms/ocifam_titres.js [81]
the count shows the records creation every 100 recs, then shows this line which has nothing wrong since executed 20800 times. and the record creation goes ahead untill the end with no problem. in this case it created 77k records.
so your script is working fine but it takes a long time?
Is it always after a certain amount of time that it times out?
I dont see any other setting that i can tell you then that time out setting. If that is low then when the debugger doesnt get anything for a while it will timeout.
If you somehow can create a sample that i can look at please make a case for this.
hang on, the value is back to 3600s after eclipse restart, maybe I had to kill eclipse when I changed the setting yesterday, and this would be saved upon normal exit only? I’ll double check this value on next problem.
(I sometimes kill eclipse when the smart client is busy for 1 hour and I can’t stop the process. not all situations can be stopped the clean way. I now worked on large tables)
killing would be a problem
I would change the value (to 0)
And restart servoy developer once and look at the value again.
just did it before answering the previous post, and it keeps it, but I did a normal exit of eclipse this time. I’ll re-check if the time out happens again.