I had the same problem. This happens when a stateful session bean has
been passivated and the serialized form of the bean is removed from the
passivation store.
The quick fix is to edit the standardjboss.xml file. In the
element for the Standard Stateful SessionBean,
there is a element. Change
That makes sense -- thanks.
Are there any configuration changes I have to make to deployment or service
descriptors when I move from 3.0 to 3.0.4, or should what I have for 3.0
work in the upgraded version, too? If there are modifications, is there any
documentation listing the needed changes?
T
