Build 605, Sun 1.4.1_01, Linux kernel 2.4.10. My node, after a variable
number of hours stops doing anything, because the OS does not allow it
to make more threads. It reports a Java out-of-memory error, but it
seems to really be a not-allowed-to-start-a-thread error. There seems
to be a per-user limit of about 550 threads (SuSE 7.3). All the threads
in use gradually drop out of use. Currently I have 7 threads in use, a
thread pool of 550, and mainport works sufficiently to tell me that
there are no open connections, and jobs due 12 hours ago have not yet
been done. This happens identically with maximumThreads set to 60, -60,
120, -120. Does maximumThreads actually do anything at all (apart from
the - flag)? Is there any way of discarding threads from the thread
pool so that the node can make a new one? Is there any way of getting
it use a thread from the 550 in the pool rather than beg the OS for a
new one?
--
Roger Hayter
_______________________________________________
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
