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





------- Additional Comments From [EMAIL PROTECTED]  2003-09-23 06:54 -------
Yep, totally agree with you.  It's got to be an OS or at least JVM bug.  I'm
guessing everyone is on Sun boxes.

I've previously filed a bug with java.sun.com.  But won't find anything out for
a couple of weeks more.  Its in java.sun limbo state at the moment.

We are also using virtual network endpoints on a single box, its a high end
production box.  I wonder if others are too?

I'm not sure what effect your change has, this error was the only one we were
getting, I assumed that socket was thrown away, but it was probably still
working (after the exception), since the exception was previously being caught.
 Now that you are letting the exception go higher, will those threads keep
processing requests?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to