|
|
Hi there,
some followup to the problem quoted below. Eventually, I've found the order of jars on classpath does not seem to be the culprit; the problem seem to be caused by...
occasionally (not too often), we are running a background import task, which uses its own EO stack: at launch, it creates a new EOObjectStoreCoordinator (and for it it creates an ERXEC and uses it to import data). When done and saved, the coordinator is disposed and released.
I don't have an answer to your specific EOObjectStoreCoordinator woes, sorry.
Could you run your background task in a separate instance or machine? For high resource background tasks that's what we do, running a specialised instance on-demand, which uses JGroupsSync to coordinate with other machines and instances when needed.
Regards,
--
Matt
|
|