Hi. >Currently locking is a ODMG-api feature, thus it does not help. Further >on to make 'safe locks with different JVM' you have to use the >persistent locking mode, this will slow down performance.
I meant using locking as demonstrated in 'OptimisticLockingTest' junit testclass... (maybe you meant the same) >Which database do you use? > >regards, >Armin currently we use HSQL as an embedded database, but upscaling is very well possible, depending on customer demands. Using the embedded database (one webapp/one database), the problem does not occur. I stumbled on this problem looking at the sequencemanager code because i 'loose' numbers upon shutdown/restart of ojb (even with grabsize to 1 .... hey.. i now realize i should put the grabsize to zero)! Roger janssen ************************************************************************* The information contained in this communication is confidential and is intended solely for the use of the individual or entity to whom it is addressed.You should not copy, disclose or distribute this communication without the authority of iBanx bv. iBanx bv is neither liable for the proper and complete transmission of the information has been maintained nor that the communication is free of viruses, interceptions or interference. If you are not the intended recipient of this communication please return the communication to the sender and delete and destroy all copies. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
