db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Nitz ...@ukr.net>
Subject Re: [PFE] locking via database for multi-VM environment
Date Sun, 28 Dec 2003 17:10:23 GMT
Hi Armin,

On Thursday 25 December 2003 23:26, Armin Waibel wrote:
> This code will definitely work in non-managed environment. If you using
> a managed environment (e.g. j2ee conform appServer, Tomcat+JTA) per
> default all created connection/DataSource are associated with the
> running transaction. When using these connections it's not allowed to
> change autoCommit state and it's not allowed to do commit or rollback.
> So, if you ask OJB for a new PB instance with a new connection this
> connection will be normally associated with the running tx (in most
> cases you will get different connections handles of the same connection).
> Thus we need a separate connection-descriptor with
> - an ordinary direct jdbc connection to DB (or to inMemory DB)
> or
> - an DataSource configurated not to be automatic associated with tx
> Shouldn't be problem ;-)

Thanks for your explanation, I agree.

> hmm, in our feature list we say "Distributed Lockmanagement", but
> current persistent lock manager does not work. From that point of view
> it's important. But I don't know if it is possible to implement your
> proposed lock manager before 1.0, because time is short!
> What do you think?
I think it would be better just to remove "Distributed Lockmanagement" from 
the feature list. I can't promise that I will do this in a short time limit, 

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

View raw message