• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Entirely independent EOF on Quartz Threads - How to do?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Entirely independent EOF on Quartz Threads - How to do?


  • Subject: Re: Entirely independent EOF on Quartz Threads - How to do?
  • From: Alexis Tual <email@hidden>
  • Date: Thu, 16 Feb 2012 22:58:08 +1100

Hi,

You should carefully read the source of BackgroundTasks and watch Kieran's presentation.
You should directly lock ec's not the osc. If you got deadlocks, that maybe causes by ec's or eo's shared between threads, you should instead pass globalIds and retrieve the eo in each thread with ec.faultForGlobalId.
Then if you have massive eof processing going on in parallel, you should use a OSC pool.

Good luck

Alex

2012/2/16 Paul Dunkler <email@hidden>
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.
// Job Start
EOEditingContext anEditingContext = ERXEC.newEditingContext();
anEditingContext.rootObjectStore().lock();

// Job Execution

// Job End
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


 _______________________________________________
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

References: 
 >Entirely independent EOF on Quartz Threads - How to do? (From: Paul Dunkler <email@hidden>)

  • Prev by Date: Entirely independent EOF on Quartz Threads - How to do?
  • Next by Date: ERRest
  • Previous by thread: Entirely independent EOF on Quartz Threads - How to do?
  • Next by thread: Re: Entirely independent EOF on Quartz Threads - How to do?
  • Index(es):
    • Date
    • Thread