Hopbot log for 2007-12-05 - Helma IRC channel: #helma on irc.freenode.net

2007-12-05:

[11:47] <hypersmil> is it possible to stop a cronjob without restarting an application?
[13:05] <zumbrunn> hi hypersmil
[13:05] <zumbrunn> app.removeCronJob or whatever it's called doesn't help?
[13:05] <zumbrunn> http://helma.zumbrunn.net/reference/app.html#app.removeCronJob
[14:31] <hypersmil> zumbrunn: doesn't work, app.getCronJobs seems to be also empty, the cronjobs are specified in the app.properties file ...
[14:38] <hypersmil> i thought about simply killing the thread but i don't know hot to get it out of the thread group -> calling enumerate would be a solution but i would need a java.lang.thread array and i don't know how to create it within helma
[14:43] <zumbrunn> seems to me the cron job related app methods *should* be able to work with cron jobs that are defined via app.properties, no?
[14:43] <zumbrunn> wanna file an enhancement request in the bug tracker?
[14:46] <zumbrunn> the cron property in app.proeprties isn't even listed in the docs, I see
[14:46] <zumbrunn> http://helma.org/docs/guide/properties/listall/
[14:46] <zumbrunn> fixing...
[14:46] <zumbrunn> is http://helma.org/development/rfc/cronjobs/ accurate from what you can see?
[14:48] <hypersmil> i think the default timeout is 60 seconds, thats currently not mentioned
[14:49] <zumbrunn> that's a separate property, schedulerInterval
[14:49] <zumbrunn> (assuming that applies for cron jobs defined via app.properties as well)
[14:50] <hypersmil> no, i mean the timeout not the interval
[14:50] <zumbrunn> oh, yes
[14:50] <hypersmil> schedulerinterval works fine
[14:52] <hypersmil> but there is a *strange/wrong* log entry "Cron jobs still running from last minute..."
[14:54] <hypersmil> do you know how i could get the threads out of the threadgroup within javascript?
[14:55] <zumbrunn> no idea
[14:58] <hypersmil> is there a way to call a specific method, enumerate would do the job but it can be called with a thread and a thredgroup array - and helma/rhino doen't know which one should be called ..
[15:04] <zumbrunn> maybe it's easier to fix the app methods to work with these cron jobs than work around the problem
[15:04] <zumbrunn> so, I suggest you file the enhancement/bug or ask on the mailing list rather sooner than later
[15:05] <hypersmil> i'll file a bug report - seems to be more effecitve than using the mailing list :)
[15:05] <zumbrunn> yep, unless you want to focus more on asking about a workaround
[15:06] <hypersmil> well, as you said fixing/enhancing is better than working around the problem this time ...
[15:12] <hypersmil> disabling cronjobs from within the application would require to rewrite the app.properties dynamically - currently you can stop a cronjob from beeing executed the next time - by simply writing a # in front of it ... - when you disable it within the application and this would not happen i think it is inconsistent
[15:18] <zumbrunn> so, that's your workaround... rewrite the app.properties dynamically
[15:19] <hypersmil> no, i thought about disabling the cronjob, rewriting the app.properties dynamically or by hand won't stop a "in progress" cronjob
[15:22] <zumbrunn> right, so... not really related to the existing cron app methods after all
[15:23] <hypersmil> http://helma.org/bugs/show_bug.cgi?id=580
[15:23] <hypersmil> (just for the records :)
[15:44] <zumbrunn> keeping cronjobs defined in app.properties and those defined in code separate from each other was probably a good design decision
[15:44] <zumbrunn> I don't think I'd want app.removeCronJob to rewrite my app.properties file
[15:45] <zumbrunn> a way to get to running cron jobs and kill them would be nice, though

 

 

In the channel now:

Logs by date: