That's because the conversation is created in the first request, and if you delay the response then the remoting client won't know which conversation id was created. One alternative is to start your conversation when you first render the page and manually set the conversation id like this: | Seam.Remoting.getContext().setConversationId(#{conversationId}); | That way the remoting calls will know which conversation context to use. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021423#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...