[Bug 46284] Add flag to DeltaManager that blocks processing cluster messages until local applicaiton initialization is completed

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=46284

Mark Thomas <ma...@apache.org> changed:

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

--- Comment #3 from Mark Thomas <ma...@apache.org> ---
I've been looking through the Tomcat code and the essential behaviour appears
to be the same all the way back to 6.0.18 (it did change in 6.0.18 in a way
that looks to be helpful to the use case).

The session state is transferred when the Manager is started. As of 6.0.18, the
ServletContainerInitializers (for 7.0.x onwards) and ServletContextListeners
are triggered before the state transfer is started. The only application
initialisation that has not been completed at this point is starting the
filters and the loadOnStartup Servlets.

While it should be possible to swap the order of the Manager start, Filter
initialisation and loadOnStartup Servlet processing, I can't think of a good
reason that justifies one order over another. The important order for me is the
SCI and SCL vs Manager start and that is already the 'right' way around for the
use case described in this bug report.

Therefore, I am resolving this as WONTFIX. If we revisit this, my instinct is
to look at simply delaying the request state transfer although that looks much
easier for the DeltaManager than the BackupManager.

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