Having done some further reading around the QueuedPessimisticEJBLock, can anyone confirm this understanding:
This Lock is responsible for managing both TRANSACTION based and NON-TRANSACTION based access to a specific entity bean instance, so as to conform to the EJB spec's requirement of providing MethodLocks AND TransactionLocks This lock ensures no two threads can access a bean concurrently - irrespective of which COMMIT option, Database Transaction Isolation Level, and CMT Transaction Type is used. Does this also mean that only one thread can get a Remote reference to that bean at any one time? Or is it still feasible that multiple clients can hold a reference to a specific Entity bean, yet are unable to make calls on that bean whilst another bean is executing a method OR has an uncommitted transaction running? Cheers, Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870935#3870935 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870935 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
