"ALRubinger" wrote : https://jira.jboss.org/jira/browse/EJBTHREE-788 | | Seam is requesting a bump of the default SFSB timeout (==passivation, not removal) from 5 minutes to at least 30. | | | | But the real nagging point is that EJBTHREE-788 does not specify *why* this needs to be done; Brian notes in a discussion w/ Pete that likely managed objects stored in HttpSession get out of sync when references to these are unbound upon SFSB passivation? | | No, the request is for removalTimeout, which talking to ALR appears to have been set to "never". This is a totally different issue from passivation/activation... Seam users are still reporting problems in 4.2.2 with SFSBs getting removed even with "never", so we need to continue monitor this... On this unrelated issue, which you ask about - no with Seam 2 we can't get restore the conversation in SFSB passivation/activation call, as we store conversations in the HTTP session, and this isn't available in these passivation/activation call backs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182476#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...