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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-04-07 14:55 ------- Why would you set tcpSelectorTimeout to 1000ms? The tcpSelectorTimeout feature is in place because of a bug in java NIO. If your NIO is working bug free, then tcpSelectorTimeout should be 0, cause the selector should wake up by itself when it receives a package. In many Unix JDKs this is not the case, hence you can set it to 50ms. I am setting this to INVALID, cause 1000ms in tcpSelectorTimeout is wrong. The problem is in Java NIO, not in Tomcat, hence you have to set tcpSelectorTimeout to a reasonable value. On windows you can set to 0, no timeout, cause on windows NIO works well, and the selector wakes up by itself when a data packet arrives Filip --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
