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
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
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
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
