The stateful session bean has timeout.
The default is passivate the bean to disk after 10 minutes,
and remove after 30 minutes.
If I understand well, the bean is passicate after 10 minutes and after 30 minutes the Bean is removed, if there is no call to it.
If you call the bean when it is already removed by JBoss should create a new instance I guess? So the Exception I got prooves that this is not the case. It is trying to read the serialized Bean but it is removed?
So increasing those values will help me for a while but the problem will still occur but no that fast?
Is this correct? Are there other sollutions?
No JBoss will not re-create the instance after it has been
How can it? It does not have the state of the removed bean,
the state is gone.
Increase the lifetime to whatever is appropriate.
It is a tradeoff between how long idle sessions last
and how much disk space is used storing that information.