The best thing to do is to make a testcase and see what happens.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114409#4114409
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114409
__
If there are more than one threads from a single client, can they access the
same SLSB simultaneously? If so, what exception would be thrown?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114405#4114405
Reply to the post :
http://www.jboss.com/index.
What you miss is that SLSBs *can* have internal state, e.g. a cached datasource
handle that they re-use to serve incoming requests.
Stateless is the interpretation from a client's point of view, so if a SLSB has
3 methods, a client should be able to call those methods on different bean
instance
"[EMAIL PROTECTED]" wrote : No. A bean is always guaranteed to be called by one
thread at any given point.
May be I'm wrong about SLSB because I'm not strong with EJB, but I really don't
see any sense in this guarantee. If code hasn't internal state it is thread
safe, so any constraints are exce
No. A bean is always guaranteed to be called by one thread at any given point.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112828#4112828
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112828
I think that it depends on internal implementation of an application server. As
I understand a SLSB should not has internal state. In this case, in theory, one
instance of the SLSB enough to serve all client's call.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic
I believe the multithreaded calls on the same handle will go to different bean
instances.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112410#4112410
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112410
Ok...What about the case where I have retrieved a handle to a single instance
of a StatelessSessionEJB up front. Then multiple client threads try to invoke
methods on the bean. Do they go to multiple EJB's as you suggest? If I look at
the MBean for the EJB I only see 2 beans created.
View the
Stateless session beans do no have identity so every concurrent request will
actually be directed to a different instance from the stateless session bean
pool. The server dynamically manages the pool size to deal with the request
load.
View the original post :
http://www.jboss.com/index.html?m
