Re: Quartz Scheduler -- Clustering

Thanks, I did see those, I’m not certain how much I misunderstood but I think I’ve got the hang of it now perhaps. I think one trouble is I’m on an unfortunately old version right now, but also I was under the impression that the Wonder framework somehow used the Database as a central authority

Re: Quartz Scheduler -- Clustering

Hi Jesse, I think you should spend some time reading the documentation. Here are some pointers: - https://www.slideshare.net/slideshow/framework-principal/23337152 - https://www.slideshare.net/slideshow/co-scheduler/9169056 - https://www.slideshare.net/slideshow/co-scheduler-indepth/13551537 The

Re: Quartz Scheduler -- Clustering

I was somehow certain that only one instance could pick up a job in the first place! You basically run a single instance for the job queuing and that works okay? I notice you have a separated didFinish and finishInit call set there far later than mine. I figure I’m loading before the properti

Re: Quartz Scheduler -- Clustering

I do not have startup problems and use these properties to disable job by default and only start then on the designed instance: er.quartzscheduler.schedulerServiceToLaunch=true er.quartzscheduler.triggersAutomaticallyPaused=true On the instance that should run the tasks I set er.quartzschedule

Re: Quartz Scheduler -- Clustering

Thanks, I seem to have found that by initializing Quartz in my Applicaiton main(), very early even — I have it working but I GET TWO EMAILS! I have two instances and they both send the same notifications. Grrr... I was sure I read code that was locking the Database and I figured a date or somet

Re: Quartz Scheduler -- Clustering

Hi Jesse, I would try to set the main log level to debug and look at the entries... There is maybe some hints there. In WOApplication, the code will print uncatched exception to stderr, make sure you capture this output. /* 556 */ NSLog.err.appendln((Object)("A fatal exception

Re: Quartz Scheduler -- Clustering

I have the scheduler working but somehow on production, (which is in a container) it simply craps out seemingly right around the time Quartz rolls in. So the app starts up and connects to RDBMS as normal. A few seconds in, around the time I would expect Quartz to load up and query- it dies. B

Re: Quartz Scheduler -- Clustering

Hi Jesse, I use ERQuartzScheduler in some apps, there is a Readme file in the source documentation folder that explain the basics. In my case, I start the scheduler on only one instance and add a entity to have the Job schedule persists in the database. Running multiple instances of a schedule

Re: Quartz Scheduler -- Clustering

Thanks Paul! It IS ERQuartzScheduler.framework but having never gotten it fully working, I cannot say if it was a good idea or not. I do have a scheduler job and that populates a number of email jobs, no real reason for the emails being jobs but it’s working and I suppose it’s a good idea. The

Re: Quartz Scheduler -- Clustering

Hi Jesse, On 12 Feb 2025, at 10:34, Jesse Tayler via Webobjects-dev wrote: > I’m trying to get Quartz Scheduler working in my project and was able to > create jobs and a scheduler to call for them to be produced and put into > queue - all runs well. > > However, I worry that I’m not in Clus