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=28161>. 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=28161 Replication messages get lost with AsyncSocketSender [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2004-04-02 15:57 ------- Async data send means that there is not time guarantee for when the session is delivered. The session should not get lost without any error trace in the logs. I am still debating whether to remove this feature all together, but I left it in for people to play with. I have not found a case where async is useful, but I am sure there is which is why it is still there. Most of the time people want to be ensured that the session gets replicated, that is when pooled mode comes in. also, from experience, using mod_jk in high load can result in "lost" sessions, cause it sometimes messes up the request and looses the session id. from my experience, pen (siag.nu/pen) works better as a load balancer I strongly suggest to retry the same test with replicationMode="pooled" and see if you get better results. Pooled means that replication is synchronous, but on concurrent channels. Filip --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
