i had this exact same problem. You can somewhat improve things by adding a delays or queues as you've done but it is not a good solution as the problem can still occur - just less frequently, or under more rare circumstances. This can also occur if a user clicks on an a4j:commandButton too quickly. I honestly don't know of a good solution to this problem, and it really does make using a4j + conversation scoped beans unappealing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110208#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...