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. -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] Mirko Herzog wrote: > Dear all > > > > We are using Resin 3.0.21 at the moment on a Windows 2003 box. We have > two services installed, ResinA as main service, ResinB configured as a > backup. Recently, we started using the run-at configuration for a job to > be executed every night. Unofrtunately, the job always gets executed > twice, resulting in performance and other various problems. Stopping the > ResinB service resolves this issue, but is understandably not a > permanent solution. > > We then switched to CronResources, but the problem still exists. Every > job specified gets executed twice. > > > > Was there a bugfix in one of the newer versions regarding this issue or > do we have a false understanding of how this feature is supposed to work? > > > > Best Regards > > Mirko Herzog _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
