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 36540] New: - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11
Date Wed, 07 Sep 2005 10:40:53 GMT
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=36540>.
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=36540

           Summary: pooled cluster replication does not seem ensure
                    synchronized replication in tomcat 5.5.11
           Product: Tomcat 5
           Version: Nightly Build
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina:Cluster
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: bachhube@fmi.uni-passau.de


If I understand it correctly, the pooled replication should ensure the
availability of the session on all cluster nodes as soon as the request is
finished. It doesn't seem to do that with the following test-case:

The attached simple webapp (clustertest.war) just prints the content of the
session entry "host" and then stores its hostname in that entry. 

This webapp is installed on 2 tomcat 5.5.11's, tomcat1 and tomcat2, and mod_jk
is used as a load balancer, sticky sessions are disabled. (Config files are
attached).

A JMeter 2.1 Test Plan is used to make requests. It repeatedly makes requests to
the webapp, waiting 20ms between the requests.

Expected behaviour:
The first request yields null, and subsequent ones return tomcat1, then tomcat2,
tomcat1, tomcat2 and so on. 

Actual behaviour:
Several requests return null, and the rest is not exactly alternating. 

In this test case, it stabilized when waiting like 50ms between the requests,
but on other webapps with larger sessions, it needed a lot more time. This is
quite serious since correctness is not ensured when not using sticky sessions.

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message