Pete said: anonymous wrote : If concurrent calls occur, Seam queues the action event for a period of time (the concurrent request timeout), if it can't process the event within that period it aborts the call and prints out a FacesMessage telling us this. Pete, if I understand you correctly, then I don't think that this is what is happening. When the period times out it doesn't just abort the call, it ends the conversation. If you compare a Conversation to a Session, you wouldn't expect a Session to expire just because a page couldn't load. As you say in option 3, something like ignoreDupRequests would be handy, but sometimes you may well want the behaviour that Vincent has coded - ie. I want all of my requests to be processed eventually (within reason). Mind you I suppose that could be accomplished with a very long timeout... I've tried increasing the concurrent-request-timeout to 10 seconds and the test page from the previous posts works fine. The calls all get queued and everything is cool and I'm a happy bunny. What are the downsides of increasing this timeout? For instance what is the danger in setting it to a stupidly large number (perhaps equal to the conversation timeout)? Thanks, Damian. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080747#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...