Re: [JBoss-user] Stateless Session remove() question
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
Re: [JBoss-user] Stateless Session remove() question
Thanks for all the fast feedback, everyone. It looks like I might as well just save myself a method invocation and not call it. Thanks again, David ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Stateless Session remove() question
No, actually, after each remote method call the instance is placed back into the pool, you can never be sure that the next call on the same remote object will use the dame instance.. Joost. -Original Message- From: Dmitri Colebatch [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 09, 2001 4:52 PM To: David Ward Cc: [EMAIL PROTECTED] 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
RE: [JBoss-user] Stateless Session remove() question
No. Only one thread at a time during a specific remote method call. Once the call is finished, the bean can take any other invocation: it is absolutely not dedicated to a particular client. If you call Remove, the container will not even forward this call to the bean ejbRemove implementation (this method is only called when the container want to remove the bean from the pool) Cheers, Sacha > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]De la part de Dmitri > Colebatch > 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. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
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
RE: [JBoss-user] Stateless Session remove() question
Don't make the call, you will avoid one network round-trip to the server ;) > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]De la part de David Ward > Envoye : mardi, 9 octobre 2001 15:42 > A : [EMAIL PROTECTED] > Objet : [JBoss-user] Stateless Session remove() question > > > 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
