DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39919>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=39919

           Summary: Slow startup when replication enabled
           Product: Tomcat 5
           Version: 5.5.17
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina:Cluster
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


The current behaviour when I have two nodes (A and B) on a cluster and both
start up at the same time seems somewhat less than ideal.

As Node A deploys context X it asks B for session data, B ignores this message
because it doesn't yet have context X active, and also asks A for session data
for X, which in turn A ignores.

A and B then sit there for (default) 60s waiting for a reply, then give up and
carry with the next context.

The net result is that it can take around 60s per webappp for a "cold" start.

I suspect that the thing to do is to reply to a request for All Session Data
with some sort of "not available here" message, rather than just ignore it
because its not one of my contexts.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to