On 1/15/07, peter ellis <[EMAIL PROTECTED]> wrote:
You will have to forgive me as im only a junior java developer but do i need to have this code declared in the xml (mina) server we are developing. Obviously the mina server is going to be dealing with multiple connections here from various clients therefore, if i declare the code you specified, do i need to worry about concurrent connections or any notions of thread reuse/pooling.
Did the ex-developer set any thread pool settings, such as the maximum number of threads? If not, you could just call the default constructor of ExecutorFilter(). Otherwise, You could pass an Executor implementation by calling some static methods in java.util.concurrent.Executors (or its counterpart in backport-util-concurrent). I believe the ex developer used the netbeans (threading) profiler
(which is what im developing in) to analyze how many threads were being created ....would i be wise to do the same anyway following the code you showed me?
Yes, I think so. :) If you just want to find out how many threads are running in a VM, then full thread dump might suffice, which is printed out to syserr when you send '-3' signal to the VM process (i.e. kill -3 <PID>) or press CTRL+BREAK in your windows console. HTH, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
