db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux
Date Wed, 30 May 2007 23:39:31 GMT
Francois Orsini wrote:
> I haven't looked at the absolute latest changes and I was wondering if 
> the case of a database being opened in a separate classloader and not 
> having been shut down properly (due to unexpected exception in the 
> application) could impede some other classloader to open the very same 
> database due to the state of the dbex.lck file, not having been 
> changed due to the exception in the other classloarder?
I think this is a legitimate concern  (assuming I can get the thing 
working to prevent dual boot) as the System property and file contents 
would still match.  I'm not quite sure how to ensure proper cleanup in 
this case.  There once was a request that we have an option that the 
database shutdown if there were no connections.  That's about the only 
way I can see to resolve it.


View raw message