I wouldn't get too hung up on the internals of tomcat here. You should
remember servlet engines can be implement the spec in any way they see
fit. They are only required to comply with the spec. Anything not
spelled out there is subject to interpretation.
Suffice it to say servlets in and of themselves should be as stateless
as possible as various threads call on their methods. Stuff that
persists for the life of the request, session, or application are stored
as attributes of the request, session, or servletContext respectively.
I'll step back here and let a tomcat developer explain the internals of
tomcat. I've only ever had a cursory look at the tomcat internal source
code. I do know the threads aren't created per request -- they are
pooled and the pool creates/drops threads as necessary. Everywhere else
they are just borrowed, used, and returned.
--David
You are correct in saying Tomcat runs a container-managed thread pool
but I was just wondering what kind of pooling mechanism it utilizes.
Tomcat appears to be not only implemented elegantly but confiding
itself in simplicity.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
