[jboss-user] [JBoss Seam] - Re: Manager.switchConversation via Ajax4JSF actionListener d

Forget the previous post, didn't work either. However, I found out that the cases in which the ce.lock() call fails is when the thread trying the ce.lock() is not the ConversationEntry's lock owner. I guess that's exactly the point of this whole locking story, but I don't understand why there are two threads in play here. For example, the Debug View shows that the active thread is: Daemon Thread [http-0.0.0.0-8080-2] (Suspended (breakpoint at line 802 in org.jboss.seam.core.Manager)), while the Variables view shows that ce.lock.sync.owner is Thread[http-0.0.0.0-8080-3,5,jboss] Wouldn't that mean that my browser was using two threads to (concurrently) access my web application (forcing Tomcat to accept the second client thread's request on another server thread) and that the second thread tried to ce.lock() a conversation entry that was not yet unlocked by the first thread? Karl View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120469#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...