tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51445] Tomcat 7 SingleThreadModel Problem
Date Thu, 30 Jun 2011 08:14:57 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51445

--- Comment #6 from Felix Schumacher <felix.schumacher@internetallee.de> 2011-06-30
08:14:57 UTC ---
I think Mali is right and his test case is valid.

If you try the servlet in a freshly downloaded tomcat you will get "0" as
result. If you spice up his testcase a little bit, you will see, that one
instance of the servlet will get initialized and another one will be used for
the request. That is what SingleThreadModel is for.

I think the logic changed from 6.0 to 7.0 that there is only one
(StandardWrapper-wide) instance variable which tells tomcat whether the servlet
is initialized or not. This initialization has moved to allocate. That means,
that one servlet gets initialized and every other newly created instance for
the pool (instancePool) will not be initialized.

In tomcat6.0 I believe the newly created servlets were initialized in
loadServlet.

Marks testcase could be testing the wrong thing by providing an instance for a
SingleThreadModel-servlet on its own.

Could that be?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message