Well you could use conversationList but how do you know what conversations are in use? The user could use several windows so many conversation could be active. The (only) way do solve this (if it really needs solving) is to extend s:link (or similar) with a new propagation, say, endAndBegin and one extra parameter, conversationIdToEnd. The server (probably SeamPhaseListener) will do exactly the same as with begin plus that it will set the timeout to 0 or promptly end the Conversation with the conversationIdToEnd. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067562#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...