Re: looong saveChanges in a background task
Re: looong saveChanges in a background task
- Subject: Re: looong saveChanges in a background task
- From: OC <email@hidden>
- Date: Wed, 25 Feb 2015 10:40:32 +0100
Chuck,
On 23. 2. 2015, at 20:01, Chuck Hill <email@hidden> wrote:
>> I’d use a different EOF stack but NOT from ERXObjectStoreCoordinatorPool.maxCoordinators which gets shared between requests. You want one that is not shared and is dedicated to the import task.
>
>> For this, just
>> EOObjectStoreCoordinator osc = new EOObjectStoreCoordinator();
>> ERXEC ec = ERXEC.new(osc); // er something like that just typed this from memory
Hmmm... I did, and my testing went well. From the server though now I'm now getting reports
===
A fault was fired while another fetch was in progress and no other channels were available to process the fault. Either make sure not to touch faults while fetching, or register more channels with the EODatabaseContext (perhaps in response to the EODatabaseChannelNeededNotification). Original Exception:N/A
===
Does that make any sense? Indeed I am not observing EODatabaseChannelNeededNotification and creating channels on-demand; on the other hand, till now, I have never seen this problem, not even when I used to set ERXObjectStoreCoordinatorPool.maxCoordinators>1.
Might it be related?
Thanks,
OC
_______________________________________________
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