Hi Shelly, SFSB are like HTTPSession but they have to take care of max-beans-in-cache tag as well. If your max-beans-in-cache is Reached before idle-timeout-seconds is over then they will be passivated.
If they are passivated then they should be called with in idle-timeout-seconds Otherwise they are deleted from hard disk as well For more details: http://edocs.bea.com/wls/docs61/ejb/EJB_environment.html#1031433 <snip> If max-beans-in-cache is reached and EJBs in the cache are not being used, WebLogic Server passivates some of those beans. This occurs even if the unused beans have not reached their idle-timeout-seconds limit. If max-beans-in-cache is reached and all EJBs in the cache are being used by clients, WebLogic Server throws a CacheFullException </snip> HTH, Saroj -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]] On Behalf Of Shelly Singh Sent: Monday, December 16, 2002 9:44 PM To: [EMAIL PROTECTED] Subject: Idle Time out Hi All, I have a stateful session bean deployed on Weblogic server 6.1. I have set the idle-timeout-seconds for it to 30 secs. The client to the bean creates a Bean Remote and goes to sleep for 40 secs. And then tries calling remote methods on the bean. The conversational state of the bean is maintained even after idle-time-out. Could anyone explain this behaviour. Regards, Shelly ========================= 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". =========================================================================== 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".
