DO NOT REPLY [Bug 36540] - pooled cluster replication does not seem ensure synchronized replication in tomcat 5.5.11

[bu...@apache.org]

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 bachhube@fmi.uni-passau.de  2005-10-04 14:13 -------
(In reply to comment #12)
> The differenc between 5.5.9 and 5.5.11 is that waitForAck is on default false
> for all sender modes. 
> Can you check with this config:
<snip>

The waitForAck was my problem indeed. Thanks you very much for pointing out. 

But now I'm a bit confused about the difference between pooled and
fastasyncqueue cluster replication really is. The docs state "synchronous
replication guarantees the session to be replicated before the request returns."
But obviousely waitForAck is the controlling setting. Isn't it best to just
ignore the waitForAck setting and have it set false for fastasyncqueue and true
for pooled? 

The docs also state that "Asynchronous replication, should be used if you have
sticky sessions until fail over", which implies that pooled should be used else.
But as this bug report turned out, sticky sessions are mandatory for correct
clustering. Maybe you should change the docs accordingly (This should go into
another bug report imo, but my bug 36542 was resolved as duplicate)

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