If you want to use locking accross multiple VMs you have to activate persistent locks in OJB.properties:
# The LockMapClass entry tells OJB which concrete LockMap # implementation is to be used. # If OJB is running in servermode it is recommended to use the # PersistentLockMapImpl. It guarantees to provide Lockamanagement across # multiple client JVMs. # If not running in OJB server mode (e.g. in desktop apps, or in a servlet # engine) it is save to use the InMemoryLockMapImpl. Using it will result # in a large performance gain. LockMapClass=org.apache.ojb.odmg.locking.PersistentLockMapImpl # LockMapClass=org.apache.ojb.odmg.locking.InMemoryLockMapImpl cheers, Thomas > -----Urspr�ngliche Nachricht----- > Von: Will Jaynes [mailto:jaynes@;umich.edu] > Gesendet: Donnerstag, 31. Oktober 2002 15:15 > An: [EMAIL PROTECTED] > Betreff: object transactions and locking > > > I'm new to OJB and to ODMG and am unsure about the full extent of the > object transactions and locking. Suppose I have a client side > application using OJB. Does the object locking work eventhough two or > more clients are running in two or more JVMs? > > Will > > > -- > To unsubscribe, e-mail: > <mailto:ojb-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:ojb-user-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:ojb-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:ojb-user-help@;jakarta.apache.org>
