Hi All—
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 Cluster-capable mode? RAM only?
If I print out a few meta properties from the scheduler, I see I’m on the RAM
store
TruAnonSchedulerJob Scheduler Name: DefaultQuartzScheduler
TruAnonSchedulerJob Scheduler Instance ID: NON_CLUSTERED
TruAnonSchedulerJob Job Store Class: class org.quartz.simpl.RAMJobStore
TruAnonSchedulerJob Thread Pool Size: 10
I did not see reason to use EOs for my Job but now I think this is the Wonder
way to cluster? Use the database?
public boolean isEnterpriseObject() {
// TODO Auto-generated method stub
return false;
}
Does this matter?
Do I need my top job to be an EO that returns true and stores a few standard
keys in the database in order to keep instances from stepping on each other’s
toes?
first_execution_date and job_description and next_execution_date and a few
others
Perhaps simply using an EO for my job CREATES the Wonder style clustering I’m
worried about?
Multiple instances? I worry they will each send out email if I use only RAM?
The Framework didn’t create any model or migrations —
Does anyone know for sure?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
