On the earlier question, concurrent request timeout is the timeout on concurrent requests in the same conversation. Seam serializes client requests in a session. If a second request comes in while another is still active, the request will block for concurrent-request-timeout ms. The conversation-timeout is what determines the conversation timeout. It is a couple orders of magnitude larger. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996331#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...