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 ------- Additional Comments From [EMAIL PROTECTED] 2005-09-20 19:36 ------- (In reply to comment #9) > Christoph, if the scenario that you have is a single client thread per > session, > then let us know, otherwise we will close this bug. My Test Case above is actually quite simple. A single JMeter thread runs subsequent requests on a cluster of 2 Tomcat servers. A jk load balancer without sticky sessions (for testing only) does the distribution. The jsp page just stores the hostname of the tomcat server in the session. No fancy multi-threading or anything. TC 5.5.9 handles the situation correctly and replicates the session before finishing the http request. 5.5.11 does not. So pooled replication in definitely broken. Please either fix it or document that it's broken. If you should choose not to fix it, pooled, synchronous and asynchronous replication modes are basically useless and should be removed. Thanks for pointing out that the servlet specs (SRV.7.7.2) state that "Within an application marked as distributable, all requests that are part of a session must be handled by one Java Virtual Machine1 ( JVM ) at a time." But in my opinion that means that when the requests are finished, the session state should already be replicated on all other cluster members. A Session with a single 7 char String object seems to need about 20 ms to replicate in my setup. Busy servers with large Sessions may get into some hundreds of ms and this is a problem for me. Bye, Christoph -- 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]
