-
1. Re: Strange Stateful Session bean Exception
raja05 May 27, 2003 4:53 PM (in response to sczapek)Increase the value of max-bean-life in your configuration. The way the beans are removed is based on this
(max-bean-life) - (max-bean-age)
By default, max-bean-life is 1800(30mins) and max-bean-age is 600(10mins). So if any beans exceeds this, it gets deleted. Look in LRUStatefulcontextcachepolicy.java's run method.
-Raj -
2. Re: Strange Stateful Session bean Exception
tommo Jun 5, 2003 7:09 AM (in response to sczapek)We are having the exact same problem and were originally delighted to see this thread, except - what is the answer?
Surely increasing the suggested value simply means that the bean will disappear at a different time interval?
Raj, would you care to elaborate?
Thanks. -
3. Re: Strange Stateful Session bean Exception
ibruell Jun 5, 2003 9:24 AM (in response to sczapek)Are there any other errors ? Something like could not passivate or error during passivation ?
-
4. Re: Strange Stateful Session bean Exception
raja05 Jun 5, 2003 10:44 AM (in response to sczapek)Hi Tommo
Do you have a timeout associated with your sessions? Make sure that your
(max-bean-life - max-age-life) is equivalent to that interval. That case, you should never have this exception as your HTTP sessions should expire that point.
-raj -
5. Re: Strange Stateful Session bean Exception
tommo Jun 10, 2003 5:43 AM (in response to sczapek)Thanks for the suggestions guys, both relevant.
We have resolved the problem - the scope for the bean in our JSP was "application", we have now changed this to "session" - this was/is a tricky one for us as we slavishly followed the Sun Duke's Bank Application model - our application is under review and the overall design will be modified.
Tom.