I see that constructing ERXObjectStoreCoordinator(true) is another way to work around the issue of closing the db connection. However, I still get two connections created and only one closed when disposed. John On 13 Mar 2014, at 14:33, John Pollard < email@hidden> wrote: Thanks Aaron, half way there, that closed one of the two connections, but neither of mine were closing so still one left open after the following code? John On 13 Mar 2014, at 13:04, Aaron Rosenzweig < email@hidden> wrote: Hi John,
Yes, that’s a known Apple bug. It creates an extra one to read “Database info” and then never releases it. There is a Wonder method to close database connections like that.
ec.dispose(); ERXEOAccessUtilities.closeDatabaseConnections(objectStore); objectStore.dispose(); Cheers,
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
|