On Tue, Sep 04, 2001 at 10:39:45PM -0500, thelema wrote: > Most of this is conjecture, but this is what I believe is causing the > problems: > > 1) the Heisenbug > There's a lot of restarts in the network; nodes aren't routing > nicely, and this part of the problem I blame on the heisenbug: a > problem somewhere between the JVM and the code that causes nodes to > pervert unique IDS changing 123456789a to 1234512345.
This one is truely weird, and I really can't imagine anything but a JVM error. I don't know how far Tavin got on it before his current jail stint (you gotta stop exposing yourself in public Tavin!)... Are you seeing Tavin's "PANIC" log entries? > 2) busy nodes > The connection limit on my node is reached very often. I'm pretty > sure this is a combination of long keepalives (many connections to > the same node which isn't the one you want to talk to) and low > connection limits. I think the whole algorithm needs to be improved somewhat. The connetion pruning code needs to run early (as soon as the connection limit is 3/4ths full or something), and should remove old connections more agressively. > 3) some sort of actual connection problem > Nodes shouldn't have any problems authenticating to each other, but > I see way too many connection problems for it to be just network > issues. I have to suspect some heisenbug in the authentication > (possibly related to the real heisenbug due to a defect in > encryption/decryption code) It's very hard to believe that an error in the stream code could cause the problem to occur in the same field every single time. <> -- 'DeCSS would be fine. Where is it?' 'Here,' Montag touched his head. 'Ah,' Granger smiled and nodded. Oskar Sandberg oskar at freenetproject.org _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
