We do not issue an ejbRemove on stateful session beans that expire while in the passivated state.
Stateless session beans only see a remove when they are evicted from the session pool, which may be only on shutdown/undeployment. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Muraly R Sent: Monday, January 26, 2004 9:29 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] <max-bean-life>? Hi Gurus, From the paid docs I have understood that this tag represents the time in sec. a 'Stateful' bean remains in the passivate store. My doubt is while removing the instance from the passivate store, does JBoss makes a call to the ejbRemove on that particular instance? The reason for the doubt being in the ejb-spec in sec:-7.6.3 Missed ejbRemove() calls, the following point explains a scenario when a call to ejbRemove is missied: A timeout of client inactivity while the instance is in the passive state. The timeout is speci- fied by the Deployer in an EJB Container implementation specific way. Also, what happens in the case of a 'Sateless' session beans, when an instance has to be removed. From the spec. I understand that a call is made(only) by the 'container', when an instance has to be removed. Thanks Muraly ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
