On Tuesday 29 January 2002 10:12, you wrote: > I'm running last snapshot on linux 2.4.8 > + kaffe 1.0.6, and fcptools + jre1.3.1 > > When Freenet usually collapse or at least crawl > (from italy the time is about 11am GMT) a lot of > hung tcp connection start to accumulate; the > status is CLOSE_WAIT. > > When they are 50+ the node degradate and cannot > insert anithing. > > When I kill fcptools the connection still exists, > but disappear if I kill the node. > > This mean that I can insert only in the morning 8( > > BTW, there is a simple way to look for version or build > number for Fred & fcptools ? Where I can find the latest > fcptools version (and be sure that it is !). > > Any suggestion ? Thanks in advance. Marco > >
Has anyone gotten Kaffe to work successfully under real load (~30+ inbound connections per minute)? I built from the Kaffe CVS head last week for my x86rh6.2 box. I couldn't get it to run the node reliably under load. It seems that that ./configure doesn't turn on native threads support by default. With green threads the node would work, but intermittently stalls for long periods (minutes). I'm not a socket guru. Could the CLOSE_WAIT issue be tied to the threading stall? I rebuilt with native thread support. That looked much more promising but Kaffe would croak with out of memory exceptions within 15 minutes of startup when running the node under typical load. I don't have the stack trace handy but the memory exception was being thrown out of Thread.start() somewhere. It's kind of a cruel joke to list Kaffe under supported JVMs on the web page without supplying the info to really make it work. --gj -- Freesites (0.3) freenet:MSK at SSK@enI8YFo3gj8UVh-Au0HpKMftf6QQAgE/homepage// (0.4) freenet:SSK at npfV5XQijFkF6sXZvuO0o~kG4wEPAgM/homepage// _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
