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.
I'm not comfortable with this for the following reasons:
1) Possible abrupt memory profile changes for our users upon upgrade that brings in this
change
2) There's nothing binding the timeouts of SFSB and HttpSession, so this makes a
problem less frequent but not properly resolve it
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?
Possible to get Seam to hook into the SFSB lifecycle callbacks and on
passivation/reactivation?
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182463#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...