My understanding is that a SLSB remove() is a no-op on the container side. A fresh SLSB instance is grabbed from the SLSB pool by the SLSB interceptor on each method invocation and returned to the pool when the method call is completed.
Fred Loney Spirited Software, Inc. www.spiritedsw.com ----- Original Message ----- From: "Dmitri Colebatch" <[EMAIL PROTECTED]> To: "David Ward" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, October 09, 2001 7:52 AM Subject: Re: [JBoss-user] Stateless Session remove() question > afaik the server will only let one thread in a SLSB at a time, so I assume > that the container will hold the instance as "busy" until you call remove. > > not based on any knowledge of the internals... > > cheers > dim > > On Tue, 9 Oct 2001, David Ward wrote: > > > Is there any benefit / penalty for calling or not calling remove() on > > the remote interface of my stateless session bean? According to the > > ejb1.1 spec diagrams, it looks like ejbRemove will only get called on a > > stateFUL session bean. Should I or should I not be calling remove() > > when I'm done? > > > > > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
