Currently, thread pools are configured for a given component,
but not for a given endpoint ...
What is the component / endpoint you are trying to configure ?
On 1/22/07, RBrinkman <[EMAIL PROTECTED]> wrote:
I've an urgent issue:
When using seda flows i configured an executor whit just one thread in the
servicemix.xml:
<entry key="flow.seda.sandbox-trace">
<bean
class="org.apache.servicemix.executors.impl.ExecutorConfig">
<property name="corePoolSize" value="1"/>
<property name="maximumPoolSize" value="1"/>
<property name="queueSize" value="1024"/>
</bean>
</entry>
This works great and every 'request' is handled by the same thread.
Since i switched to jms/jca flows by setting persistent="true" on the
sm:container this does not work any more.
I tried the following as key name:
flow.jca.org.apache.servicemix.jca.{http://tntpost.com/ddb/tryout/1.0}sandbox-trace:sandbox-trace
When i use flow.jms as key it does work but thats just to much, i'd like
only the sandbox-trace component to have one thread.
Could someone please help my out because this configuration option would be
very valuable for us.
Thank you in advance,
Rob
--
View this message in context:
http://www.nabble.com/Using-ExecutorFactory-on-persistent-flows-tf3058716s12049.html#a8504569
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
