You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by "Geigl Maximilian, R235" <Ge...@akdb.de> on 2002/11/28 19:01:29 UTC

[LOCKING] different clients, one database

Hallo,

I hope this question was not answered in previous discussions, I searched the archive but didn't find exactly an answer for my problem.

We use the same database accessed by various client applications, one of them is an OJB ODMG appllication. How can I ensure that transactions separate the differen clients correctly?

I understand the behaviour of OJB as follows:
- OJB does not lock anything on dbms level
- different threads using the same broker can be 'synchronized' by OJBn memory
- different client application that are all using OJB ODMG can be 'synchronized' by using the persistent locking strategy OJB_LOCKENTRY )

But how can I ensure consistency with clients that are not aware of OJB_LOCKENTRY?

Regards
Max