On Fri, Mar 12, 2004 at 10:33:31PM +0100, Michael Schierl wrote: > Michael Schierl <[EMAIL PROTECTED]> writes: > > > However, after a few tests (replaced Fred by a simple prog that says > > nothing but disconnects on a keypress) i can see that I get an > > IOException like the one above when the connection is closed from the > > peer, but a ConnectException when I run into a SocketTimeout. Seems to > > be some work for me to fix that (in that case it should not mess up > > the log file)... > > St00pid me... The connect exception was caused by my test app which > closed the socket and since FIW reconnects at once, it gave an > error then... The SocketTimeoutException occurring first is (as > expected) not written to the error log file. > > So, this bug is really somewhere inside freenet. Either the accept() > call was not handled quick enough (dunno how accept is called in nio) > or Fred really closes open sockets without having sent any data.
Consistently? Can you write me a test case? I need it to do it until it fails and then stop and tell me, and I can then check the logs and debug it... > > mihi -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
