StateFul SessionBean Passivation

Question

I am running a EJB application in weblogic, using StateFul SessionBean.Suppose say,
the maximum number of clients at a time is 100.(And assume that this is the maximum no of beans taht are created).Now 2 more clients 101,102 are coming.This time the 1st,2nd client are idle, so that their beans are passivated.Now What will happen,
1.Whether the container will create 2 more beans for the 101,102 client
or
2.the Clients shouold wait until, any 2 of the previously created clients going to logout
or
3.I read in EdRoman Book, the following,Excerpt
if a SF bean is passivated for a particular client.And the client again came the same bean is not necessarily to serve for that client.Any bean can activate and work for the client, from the point where the original bean is left.
If this is the case.
then the container will activate the 2 beans and give it to them(101, 102 ).And now the original client (that is 1, 2 clients ) agin they are invoking business method .Now they(1,2nd) should wait for any other 2 clients beans for passivation.

Answer 1

Thanks for the suggestion Barry, but since we are using a client application
that creates the SSB directly, there's no servlet or intermediate
server-side bean to implement HttpSessionBindingListener. I'll check, but
I'm pretty sure the SSB can't implement it itself. Still, it's food for
thought...
Cheers,
Dave
"Barry Munro" <[email protected]> wrote in message
news:[email protected]..
On 03 Dec 2001, Dave Lorde wrote:
We would like to be able to force passivation or removal of stateful
session beans whose idle timeout has expired or where the client has
disconnected. Any ideas?To remove them when your user session expires you could use
javax.servlet.http.HttpSessionBindingListener so that you are informedwhen
the user's session is unbound from the session. Then you could call the
remove method of your stateful session bean which calls the ejbRemove
method on the SSB.
Barry