I cannot figure out from the JBoss documents if a session bean get locked on method/bean with CMT.
It is clear that a entity bean and locking-policy = (QueuedPessimisticEJBLock) will have ejb level lock. But for a session bean with the locking-policy = (QueuedPessimisticEJBLock) (Actually only one place to specified the locking-policy), there is no effect with this policy. My test with a java client running 2 threads that call the same session bean and method result in the second thread do not wait untill the first call to the method ends ( if not the first transaction ends ). That is both running the same methods at the same time. So is it correct that the locking-policy does not apply to session bean? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897860#3897860 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897860 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
