I think Seam normally serializes requests within a conversation, but if you are accessing a stateful component in the session then you can run into problems like this. You'll need to add @Synchronized to your session bean to get Seam to enforce serialized access to a component across different conversations.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997563#3997563 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997563 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
