Could someone please clarify as to what happens if an idle-timeout is reached for a stateful Session bean while it is in activated state? I mean when it is still in ejb cache ? I am looking for the behavior in context to Weblogic. As per the documentation , the stateful Session EJB might be removed by the container at its discretion based on whether it is in dire need of resources. But it is not clear if the container while removing it actually calls the ejbRemove() method or not. As per EJB specs, there is a missed ejbRemove() call if the container removes a stateful session bean from the passivated state.(Section 6.6.3). But nothing seems to be mentioned in the EJB specs as well the Weblogic docs as to what is the plight of a idle-timed out Session bean in activated state when it is going to be removed. Specifically is the ejbRemove() called ? Thanks in anticipation, Mainak Datta, US Interactive Inc. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
