Oskar Sandberg wrote:
> The problem is (I guess) that > your living outgoing connections are staying alive and grabbing all the > threads, hardly allowing any incoming. This effectively creates a > situation where your node can only be routed to using the already open > connections (something that has been discussed as a feature, but which I > think we can agree must be implemented under much more controlled > circumstances). > > What clearly needs to be done is tuning the lifetime of connections. > Just setting the connectionTimeout down a little may help (why is that > the one setting nobody is messing with?), but OpenConnectionManager > probably needs to be better at pruning out connections (like removing > redundant connections to the same node) as well. Yep, I experimented a bit with connections and end easily up with about 40-50 idle outgoing connection to other nodes (with the def ConnectionTimeout setting). If you say that the default thread setting of 120 allows about 60 threads, we will quite easily run out of threads. I would suggest to either have a maxOutgoingConnections setting (but I don't like the idea of having yet another preference to be set) or to be more intelligent as when to kill idle outgoing connections in order to always prefer active connections over these. Maybe if the number of active threads is a certain threshhold under the max number of threads (e.g. 5), we should simply start killing the oldest idle connection. Sebastian _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
