DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23146>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23146 Calling socket.setTcpNoDelay causes connector to disconnect [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2003-09-23 06:37 ------- I known, I know. Mentioning your OS and VM is irrelevant, and takes time. Anyway, this error is caught (what you see is the result of a printStackTrace; I will improve the logging of this for Tomcat 5.0 by not catching an exception in setSocketOptions). The problem is that if this error occurs, I think the server socket is dead (and the VM's network stack may be too as well). So try a different VM (for ex, IBM if you're running under Linux), or apply all OS kernel patches and use the latest VM (Solaris). I don't see how this report can be caused by a Tomcat bug, rather than a VM bug. If all of the submitters use Solaris, I think it's time to head to java.sun.com and file a bug there (assuming you use an up to date system). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
