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 ------- Additional Comments From [EMAIL PROTECTED] 2004-04-05 17:26 ------- Next info: If I use this JSP, then synchronous and pooled are both EXTREMELY slow, response times between 1000ms and 5000ms. As soon as I reduce tcpSelectorTimeout from 1000 to 10, I get more reasonable response times (10- 50ms). Any idea, why tcpSelectorTimeout show such a tremendous effect? Then when I use multiple parallel clients, synchronous again gets too slow, so only pooled is an alternative. Synchronous once showed a freeze (getting no more anserws) for 15 seconds. Both, synchronous and pooled do not show the problem of missing sessions. Nevertheless I like the idea of having one or few dedicated replication connections fed by a queue of work load and not directly coupled to the finishing of the original response (asynchronous) much more. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
