Hello ranchers,
in a EJB-container, there are pools for stateless session-beans,
entity-beans and message driven beans.
In a servlet-container, there is no pool for the
servlets.
We only need one instance to service all of the requests.
I do not understand why the J2EE-components within the
EJB-container and servlet-container are handled differently.
Why is there a separate
thread for every request
entertained by the same servlet instance instead
of using a servlet-pool?
There must be a reason for this different behaviour,
but I have no clue why EJBs are using a pool and
servlets do not.
Regards
Oliver