Tavin & Scott are probably right, Fred & Kirk may be seeing lost threads in fproxy. This would be useful knowledge, so if it's possible run the proxy in a separate jvm and you should be able to tell which process owns the runaway threads. On linux, a command like this:
$ ps -eo pid,ppid,pgrp,args will show the parent process id and the process group id. I think win2k task manager is able to devine this info as well. In Kirk's top output, it looked like there were 2 groups of 9 threads, 2 groups of 4 threads and a couple of stragglers. I suspect the 2 groups of 4 are fproxy threads... 1-listener, 1-timer, 1-connection handler, 1-client. _______________________________________________ Devl mailing list Devl at freenetproject.org http://www.uprizer.com/mailman/listinfo/devl
