Hmmm.. Seems like you are the victim of some kind of deadlock issue. Two questions that would be very useful to know the answers of to be able to solve the problem:
1. What are all those threads registered as doing and what OS and JVM version and so on are you using? Can you give us all the data from http://localhost:8888/servlet/nodeinfo/internal/env 2. Where exactly are those threads stuck? It would be good if you could provide us with a complete stack dump. To generate a full dump (windows method) you need to run fred from a console and hit ctrl-Break (keep a large screenbuffer). In Linux I think you are supposed to do a kill -QUIT <PID> or something to achieve the same effect (check the mailing list archive for a correct description if this doesn't work). Regards /N > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of S > Sent: den 19 november 2003 11:47 > To: Discussion of development issues > Subject: [freenet-dev] Thread overage (by 1,000%+) > > > Hi all: > > I'm running 5038. The problem indicated below generally crops > up after a few hours of running my node, it's been taking > place for the last few builds. Everything runs just fine for > a few hours, then all of a sudden, the number of threads > skyrockets out of control until Freenet (or perhaps Java > itself) collapses with Out Of Memory errors. > > Any idea what might cause this? Symptoms are on a P3 600 with > a 10 gig store, if there are other relevant settings, ask and > I'll tell. > > Current routingTime 0ms > Curent messageSendTimeRequest 0ms > Pooled threads running jobs 6526 (1,274.6%) > Pooled threads which are idle 396 > Current upstream bandwidth usage 21 bytes/second (0.1%) > Reason for refusing connections: activeThreads(6520) >= > maximumThreads (512) > > I have the thread limit set to 512. When this problem crops > up, the disk starts thrashing like all holy hell, and > eventually Freenet dies with Out of Memory as the most recent > log entries. It's sporadic; I have kept recent builds up for > 24+ hours with no problem, then the thread overage kicks in > after a couple of hours on the next run. > > -s > _______________________________________________ > Devl mailing list > [EMAIL PROTECTED] > http://dodo.freenetproject.org/cgi-> bin/mailman/listinfo/devl > _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
