On 10/15/07, Shahm <[EMAIL PROTECTED]> wrote: > > > > Shahm wrote: > > > > Hi bysender, > > As u suggest me earlier to use thread pools, i found only the part of > > the solution , But the actual problem we found is that , the no of request > > processed is equal to corePoolSize. i.e if corePoolSize is 32, only it can > > process up to 32 requests. It seems like it is not killing the thread i > > suppose. But i donno whether this is the actual problem or is ther ny > > other reason behind this, and here z my question > > > > 1. How to kill the Pooled Thread by custom? > > 2. Is ther ny config need to be maintained while using thread pools for > > killing the thread? > > 3. Im using Logicblaze FUSE1.3.0 for deploying my JBI components , If > > possible juz tell me Itz problem with fuse or not?
This reason you're not seeing the number of threads decrease is because you have explicitly configured it to be 32. The corePoolSize is used to configure a java.util.concurrent.ThreadPoolExecutor (http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html) and serves as the lower boundary for the number of threads to keep alive in the pool. I *highly* encourage you to read the Javadoc for the ThreadPoolExecutor to understand how it works as I think this will alleviate most of your questions above. After reading that, please let us know if you have anymore questions. BTW, there are much newer releases of Fuse available for download: http://open.iona.com/ Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Apache Geronimo - http://geronimo.apache.org/ Castor - http://castor.org/
