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=28259>. 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=28259 Synchronous cluster very slow - select() bug ------- Additional Comments From [EMAIL PROTECTED] 2004-04-07 14:50 ------- Here is what causes the problem: in TcpReplicationThread line 142 the call to key.interestedOps blocks until the select in the parallel execution of ReplicationListener returns the next time. I checked with adding debug output directly nefore and after. Internet sources confirm, that register and setting interestedOps are blocking on select to the same selector. Some people suggest putting wakeup directly before register and interstedOps, but since an interrupted select in ReplicationListener will very quickly do the next select, I think you need some way of informing ReplicationListener to not do the select until interestedOps has returned. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
