tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 54507] Notification for expired session sent to still initializing servlet context
Date Fri, 01 Feb 2013 12:23:27 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=54507

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Mark Thomas <markt@apache.org> ---
Configuring an application in a Filter.init() method is a poor design choice.
Application initialization should happen in a ServletContextListener.

There is a little ambiguity in section 6.2.1 of the Servlet specification but
your interpretation (that Filter#init() must be called for all filters before
requests are served) is consistent with how the Tomcat developers have
implemented filter initialization.

That said, I do not see how the behavior you describe can occur. The background
processing method exits immediately if the component is not available - which
it isn't when the Filters are being started.

I have moved the starting/stopping of the thread since the thread can't do
anything until the start method completes so there is no point starting it
earlier. However, that shouldn't change the current behavior.

I also found and fixed a problem in Tomcat trunk where the test for component
availability was being skipped. However, Tomcat 7 does not exhibit that
problem.

Marking this as fixed due to the Tomcat 8 fix.

-- 
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