I am not totally sure (starting the test today) but I *think* it does. I
remember that I started noticing this problem when I first increased
maxmimumThreads in order to make my node use up more of my available
bandwidth
/N
___
Support mailing list
JVM 1.4.1_01 (always and ever until there is a newer one)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Matthew Toseland
Sent: den 6 februari 2003 19:48
To: [EMAIL PROTECTED]
Subject: Re: [freenet-support] Build 659 (unstable)
Are you sure you aren&#
t: Re: Longtime idle connections, was: [freenet-support] Build 659
(unstable)
On Tue, Feb 11, 2003 at 09:52:17AM +0100, Niklas Bergh wrote:
>
>
> -Original Message-
> From: Matthew Toseland [mailto:[EMAIL PROTECTED]]
> Sent: den 10 februari 2003 19:55
> To: Niklas Berg
And another one
-Original Message-
From: Niklas Bergh [mailto:[EMAIL PROTECTED]]
Sent: den 11 februari 2003 12:57
To: 'Matthew Toseland'
Subject: RE: Longtime idle connections, was: [freenet-support] Build 659
(unstable)
On this particular node maxmimumThreads are set
659 seems to have solved the 'Node suddenly ceases traffic'-problem. I
have a node that has been up for close 120 hours now and there is till
no sign of stagnation. It is serving up 13000 q/h at about 1MBit/s.
One thing though:
Peer addr Send Count Send Size Receiving Messages Idle time Lifetime
Are you sure you aren't using a nonstandard JVM? The IBM JVM has been
known to have serious problems, as has Kaffe, and old versions of the
Sun one sometimes have nasty bugs..
On Thu, Feb 06, 2003 at 10:26:25AM +0100, Niklas Bergh wrote:
> 659 would seem to have some problems with announcing. One
659 would seem to have some problems with announcing. One of the nodes I
upgraded yesterday hasn't done a single usefult thing since...
Feb 4, 2003 5:39:20 PM (freenet.node.states.maintenance.Checkpoint,
QThread-4): Executing Checkpoint: Native Filesystem Directory checkpoint
Feb 4, 2003 5:39:21
> Fix (hopefully) for the problems which were reported with a node
> getting 120 connections and then becoming unresponsive with no
> traffic. OpenConnectionManager.put() should kill enough connections to
> take us back under the connection limit, not search for enough and
> then only kill one
Build 659 is now in CVS. Within a few hours it should also be available
as the current unstable snapshot. Features:
* Avian's latest HTML filter fixes (thanks!)
* Fix (hopefully) for the problems which were reported with a node
getting 120 connections and then becoming unresponsive with no
traf
