Hi, according to the EJB 2.1 spec ejbRemove should be called either if remove is called on the bean OR if the statefull session times out. (7.6 figure 6).
As far as I have been able to find out this is not the case in jboss 3.2.3. 1. ejbRemove is called from the Statefull PM (in removeSession()), which is only called when the container see a ejbRemove cal. 2. If a statefull session times out a call to removePassivated() will happen, but no call to ejbRemove will happen here (which I guess would actually mean it would have to be activated first). FYI: the chain is LRUStatefulContextCachePolicy$RemoverTask.run()->StatefullInstanceCache.removePassivated()->pm.removePassivated() How is this to be intepreted? a) That JBoss does not follow the spec in this regard? b) Or the the max-bean-life is not to be considered as a timeout for user of a the statefull session, but only as an internal file cleanup mechanism? (Actually I still think that ejbRemove should be called when the container decides that the instance may not be available any more). Any thoughts on this? //Peter Antman View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3832698#3832698 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3832698 ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
