Quartz (http://www.opensymphony.com/quartz/) is a widely used open 
source scheduler that has much richer functionality.  It includes a JDBC 
scheduler so that a cluster of servers can know which one is running a 
given cron job.

-- 
Serge Knystautas
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. [EMAIL PROTECTED]

Mirko Herzog wrote:
> Hi 
> 
> Thanks for your answer. This sounds very logical and it's quite a shame we
> didn't figure that out ourselves. So one way to go could be writing a
> lockfile that gets checked by every JVM to see if it is allowed to run the
> job?
> 
> Ore are there more elegant solutions?
> 
> Thanks for every input
> 
> Regards
> Mirko
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Serge Knystautas
> Sent: Freitag, 9. März 2007 19:48
> To: General Discussion for the Resin application server
> Subject: Re: [Resin-interest] Problem with run-at / CronResource
> 
> Every JVM that you start will run the scheduled job, whether you have 1 
> instance, 2 instances, or 20 instances.  There is no inter-JVM 
> communication to assign responsibility.
> 



_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest

Reply via email to