db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-700) Derby does not prevent dual boot of database from different classloaders on Linux
Date Thu, 03 Aug 2006 16:52:03 GMT
great, sounds like the sync part is a non-issue.  I was stuck trying
to come up with something specific to the db shared across both 
classloaders that we could sync on.  Using this will single thread
opens of different dbs, but I think that is ok.

Daniel John Debrunner wrote:
> Mike Matrigali wrote:
> 
> 
> 
>>If anyone has ideas on this one, please post them.  I have been stumped
>>by this one so far.  As I posted earlier I think one approach simply
>>needs a way to uniquely identify the current JVM, and also some way
>>to coordinate a sync block across 2 class loaders. 
> 
> 
> A Java synchronized block across class loaders is easy, either
> of these will work. But I'm not sure if that's what you really meant,
> but I'd thought I'd throw it out there.
> 
> synchronized ("derby")
> {
> }
> 
> synchronized ("")
> {
> }
> 
> Dan.
> 
> 
> 
> 


Mime
View raw message