The problem seems to lie in org.jboss.seam.core.Manager, method
restoreAndLockConversation.
The first call locks the conversation, the next ones can't lock it and are redirected
to an error. Conversation should allow concurrent access, or at least wait for unlock
instead of going to error handling
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080205#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...