On Wed, 12 Dec 2001, Gianni Johansson wrote: > > Time (Freenet.session.FnpLink, Non-pooled connection thread: ip_address): > > Authentication I/O failure: Connection reset by peer: JVM_recv in socket
> > Time (Freenet.session.FnpLink, Non-pooled connection thread: ip_address): > > Authentication I/O failure: Connection reset by peer: socket write error > I don't think that they are errors at all. > > I'm pretty sure these are caused by hang ups from busy nodes, but Oskar could > say for sure. > The socket write error I can see as the node hanging up, its weird that it should happen so often though. But the JVM_recv thingy could be something else, I did some research on it and one forum suggested that the VM bound the socket to an already bound port. The machine that this is running on actually has alot of ports listening in the 1000 -> 3000 range so that would make sense. The exception occurs in a rather (to me) pointless InputStream.read() btw. I tried digging into the code but it was kinda confusing and involved a large number of classes ;) -- | Are ?rseth | elrond at idi.ntnu.no | http://ctemp.dhs.org/ | | tlf: 73886876 | mob: 410 00548 _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
