db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian McCallister <mccallis...@forthillcompany.com>
Subject Re: cvs commit: db-ojb release-notes.txt
Date Mon, 19 Jan 2004 14:01:37 GMT
Thomas,

I cannot find any docs on the LockServer -- is there anything checked 
in? As we are going to be using OJB in a cluster this is of particular 
interest to me (especially failover capabilities).

-Brian

On Jan 17, 2004, at 12:02 PM, thma@apache.org wrote:

> thma        2004/01/17 09:02:07
>
>   Modified:    .        release-notes.txt
>   Log:
>   1st check in of the new Servlet based distributed LockServer.
>   It's been junit tested already, and there seem to be no problems!
>
>   Revision  Changes    Path
>   1.33      +5 -12     db-ojb/release-notes.txt
>
>   Index: release-notes.txt
>   ===================================================================
>   RCS file: /home/cvs/db-ojb/release-notes.txt,v
>   retrieving revision 1.32
>   retrieving revision 1.33
>   diff -u -r1.32 -r1.33
>   --- release-notes.txt	9 Jan 2004 22:42:04 -0000	1.32
>   +++ release-notes.txt	17 Jan 2004 17:02:07 -0000	1.33
>   @@ -55,18 +55,11 @@
>    failed when DList instance itself was persisted (using 
> db.bind(...)) and
>    re-loaded within tx, but iteration over the list values was done 
> outside of the tx
>
>   +- The bogus ODMG Distributed Lockmanagement feature has been 
> replaced by a new
>   +  Servlet based LockServer. Transaction isolation should now work 
> properly even
>   +  accross a cluster of JVMs.
>   +
>    KNOWN ISSUES:
>   -- The ODMG Distributed Lockmanagement feature seems to be buggy.
>   -  (LockMapClass=org.apache.ojb.odmg.locking.PersistentLockMapImpl)
>   -  Currently locks are written to the db in the same transaction as 
> the
>   -  business logic operations. Thus locks may not be visible outside 
> the current
>   -  business transaction.
>   -  We were not able to fix this yet as compley situations in managed 
> transaction
>   -  environments must be taken in a count.
>   -  We will ship a replacement of the buggy LockManagement asap.
>   -  The InMemory Lockmanagement
>   -  (LockMapClass=org.apache.ojb.odmg.locking.InMemoryLockMapImpl)
>   -  is not affected.
>
>
>    
> ---------------------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message