Well, in my opinion, this should not behave as ms-dos or sco or whatever: it should behave like Database locks. Even if JBoss let you continue, the DB won't because you will have two different connections that try to access the same row => lock.
> ---------------------------------------------------------------------- > > Comment By: Georg Schmid (giorgio42) > Date: 2002-09-13 10:13 > > Message: > Logged In: YES > user_id=437570 > > > Bill, > > although you are right, this behaviour is a major pain. > > The default pessimistic locking reduces CMP-based apps in > JBoss into some kind of single tasking MS-DOS style crap. > > 6 year ago I had to port some kind of flock/lockf stuff from > SCO Unix to MS-DOS5.0. This would have been simple, if > MS-DOS had the same locking semantics as Unix, because > the MS compiler already provides the functions. > > The problem however is: in Unix, if a process locks a region > in a file it has locked already, the locked regions > are "merged" (it probably increments a reference count and > then continues). In MS-DOS this is not done, so a process > can lock itself out of a file region it has locked itself. > > Which is ridiculous. I had to build and maintain a list of all > already locked regions and if a region was already locked, > not try to lock it again. > > The default pessimistic locking acts like MS-DOS file > locking, where it should behave like the SCO Unix version. > > My 2 cents. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
