That should not be related. The only two causes of this that I have see are:
1. Implementing awakeFromFetch() and triggering a fetch in that method 2. An exception that leaves EOF in a dirty state with the fetch still marked as in progress I have not seen either in many years. I also, have never had to handle that notification. My advice is to catch the notification and log a stack trace as a first step to tracking this down. Chuck On 2015-02-25, 1:40 AM, "OC" wrote: Chuck, On 23. 2. 2015, at 20:01, Chuck Hill <[email protected]<mailto:[email protected]>> 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 protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
