https://issues.apache.org/bugzilla/show_bug.cgi?id=46284
Summary: Add flag to DeltaManager that blocks processing cluster
messages until local applicaiton initialization is
completed
Product: Tomcat 6
Version: 6.0.18
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Cluster
AssignedTo: dev@tomcat.apache.org
ReportedBy: [EMAIL PROTECTED]
Created an attachment (id=22928)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=22928)
A multi-file patch that includes changes that allow DeltaManager to block
processing of cluster messages until local application initialization is
complete
Suggested enhancement to DeltaManager that allows a configuration element to
control whether incoming cluster messages should be blocked until after local
applications are done initializing.
The idea is that there exist some web applications (I know of at least one
commercial app [that I happen to support during working hours]) that, when
deployed on a cluster with session replication, fails when the cluster is
implemented with Tomcat but works fine when using other application containers.
The inspiration for this enhancement is a comment from the vendor's engineering
support, who tell me that other application containers (WebSphere and WebLogic,
at least) initialize local applications before beginning to process session
replication messages from the cluster.
The attached patch gives the Tomcat user the option of continuing to begin
processing session replication messages from the cluster immediately (the
default), or block processing those messages until local applications have
completed initialization.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
