Hello,
I know this is an implementation specific question. But I am interested
in knowing what strategies vendors are using to minimize resoruce
consumption therefore improve scalability.
EJB spec describ how to perform bean pooling/swapping. But it seems to me
that if there is a reference to EJBHome/EJBObject, then you will have
one corresponding object running. So for 1000 concurrent users, there
will be 1000+ EJBHome/EJBObject object on server although most of them
idle, while we may only have 100 bean instances or so doing real work.
If a client exits or crashes, its corresponding EJBHome/EJBObject object
will be gc-ed. Is this understanding correct? How expensive are to keep
those EJBHome/EJBObject objects around (compared with bean instance?)
I thought there were some discussion touching this topic on the list,
and I just could not find it any more.
cheers
chuck
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
