Hi
As i known,when first client call a stateless session
bean(thehome.create();thehome.something(),thehome.remove()
);the container create a stateless session bean(newInstance();setSessionContext;ejbCreate(),something());when
second client(the same as firt) call a stataless session
bean,the container only run something() bessiness method.
it use the bean instance is the same first.
if many many client call the same stateless session bean
concurrently,the container use only one stateless session
bean instance,is it right? or the container create many
stateless session bean instance to response so many client
request?
thanks for ur reply!
-
About stateless session Bean (4 messages)
- Posted by: an alix
- Posted on: June 28 2001 21:25 EDT
Threaded Messages (4)
- About stateless session Bean by Shiva Paranandi on June 29 2001 00:09 EDT
- About stateless session Bean by Madhu RameshKumar on June 29 2001 00:25 EDT
- About stateless session Bean by an alix on June 29 2001 21:35 EDT
- About stateless session Bean by Shiva Paranandi on July 03 2001 04:51 EDT
- About stateless session Bean by an alix on June 29 2001 21:35 EDT
-
About stateless session Bean[ Go to top ]
- Posted by: Shiva Paranandi
- Posted on: June 29 2001 00:09 EDT
- in response to an alix
The application server can have a pool of stateless session beans and serve the clients requests. -
About stateless session Bean[ Go to top ]
- Posted by: Madhu RameshKumar
- Posted on: June 29 2001 00:25 EDT
- in response to an alix
Hai
In stateless session beans,
Container will create instance for every request..
Instances are depending on requests..
-
About stateless session Bean[ Go to top ]
- Posted by: an alix
- Posted on: June 29 2001 21:35 EDT
- in response to Madhu RameshKumar
Hi Madhu RameshKumar
"Container will create instance for every request"
why the ejbCreate() is not invocked when second client
call thehome.create()? -
About stateless session Bean[ Go to top ]
- Posted by: Shiva Paranandi
- Posted on: July 03 2001 16:51 EDT
- in response to an alix
Actually, Madhu is not exactly correct here. Not all containers will create an instance on invocation of the create on the home. An ejbCreate is only invoked if the Container feels that existing resources are not enough for servicing the client. As far as possible the container tries to invoke the existing resources. Similarly when you invoke remove then the container might not remove the bean at all from memory.
Shiva.