Originally posted by Yi Meng:
It seems that we cannot rely on ejbRemove() and ejbPassivate().
So where to put theose critical cleanup things?
As mentioned by Kathy, in the other post...the ejbRemove() method may not be called in the foll 3. scenarios :
1.
EJB Server Crash
2. SFSB timesout in a passivated state
3. An runtime-exception occurs
So in real projects, We may be required to write tools that perform a periodical cleanup of the resources, held up by the dangling stateful session beans. My guess is that Stateful session beans are not really as popular as Stateless session beans... :roll: