> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc
> fleury
> Sent: Thursday, August 09, 2001 8:57 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] new N-Lock/queued locking policy
>
>
> |To test out this new lock-policy change standardjboss.xml and replace:
> |
> |SimplePessimisticEJBLock
> |
> |with:
> |
> |QueuedPessimisticEJBLock
>
> Simple huh? thanks for pushing me in that direction Bill, Rabbit Hole is a
> better container for it. In fact I remember you wanted to do the N-Lock
> stuff for the clustering is that right? can you expand a bit?
>
Actually, I'm kind of against distributed locking in a clustered
environment. I think the database is the better place for this. We use
"select for update" in our JBoss "clustered" environment and it works fine.
I think WebLogic works in the same way now(can anybody verify?). Does
anybody know any concrete research on this subject?
Thanks,
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
