Entirely independent EOF on Quartz Threads - How to do?
Entirely independent EOF on Quartz Threads - How to do?
- Subject: Entirely independent EOF on Quartz Threads - How to do?
- From: Paul Dunkler <email@hidden>
- Date: Thu, 16 Feb 2012 11:29:31 +0100
| Hi Community,
i'm currently working on a WebObjects-Application which uses the Quartz Scheduler to schedule and run thousand but thousand of jobs. Every job is doing some work in the database (Like reading, computing and then Updating/Deleting some Details from the database).
This works quite well when i only allow Quartz to start one Single Thread for Job Execution. But when i configure more than one thread, it seams that i have problems with EditingContext / ObjectStoreCoordinator-Locking or something else.
The Question is: What should i do to achieve an entirely independent EOF-Stack per Quartz Thread? If it is possible without ramping up a complete EOF-Stack per Thread, this would be even better ;)
Currently i just tried to Create a new EditingContext per Job at the start, lock the rootObjectStore, do some things and then unlock the rootObjectStore and dispose the editingContext. But that doesn't seem to work for me. EOEditingContext anEditingContext = ERXEC.newEditingContext(); anEditingContext.rootObjectStore().lock();
anEditingContext.saveChanges(); anEditingContext.rootObjectStore().unlock();
It would be nice to get your suggestions about this Topic.
--
Mit freundlichen Grüßen
Paul Dunkler
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden