This is the default behavior of the thread pool.
It will keep thread alive for some time, so that they can be reused.
This avoid the cost of creating a new thread each time.  After the
timeout elapsed, the thread will be destroyed to avoid keeping too
much threads doing nothing in memory.

On Tue, Feb 24, 2009 at 07:37, muvvala <[email protected]> wrote:
>
> hi ,
> I have created a new EIP component. I configured the thread pool for this
> component as follows:
>
> <bean class="org.apache.servicemix.executors.impl.ExecutorConfig">
>              <property name="corePoolSize" value="25"/>
>              <property name="maximumPoolSize" value="75"/>
>              <property name="queueSize" value="0"/>
> </bean>
>
> The problem is, when I sent a request to this component using send(), the
> request is being processed sucessfully but in the Jconsole I could see the
> following stack trace related to seda-flow.
>
> Name: pool-flow.seda.servicemix-my-eip-thread-13
> State: TIMED_WAITING on
>
> edu.emory.mathcs.backport.java.util.concurrent.synchronousqueue$n...@551b97
> Total blocked: 0  Total waited: 2
>
> Stack trace:
> java.lang.Object.wait(Native Method)
> java.lang.Object.wait(Object.java:432)
> edu.emory.mathcs.backport.java.util.concurrent.TimeUnit.timedWait(TimeUnit.
>
> java:301)
> edu.emory.mathcs.backport.java.util.concurrent.SynchronousQueue$Node.attemp
>
> t(SynchronousQueue.java:374)
> edu.emory.mathcs.backport.java.util.concurrent.SynchronousQueue$Node.waitFo
>
> rPut(SynchronousQueue.java:402)
> edu.emory.mathcs.backport.java.util.concurrent.SynchronousQueue.poll(Synchr
>
> onousQueue.java:566)
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.getTask(T
>
> hreadPoolExecutor.java:498)
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.ru
>
> n(ThreadPoolExecutor.java:689)
> java.lang.Thread.run(Thread.java:595).
>
> After some time(approx 1 min) all the threads are getting cleared. Is this a
> default behaviour or did i missed anything.
>
> --
> View this message in context: 
> http://www.nabble.com/TIMED_WAITING-of-component-thread-pools-tp22176645p22176645.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Reply via email to