On Wed, May 14, 2008 at 11:52 AM, Paul Cahill <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've read a few postings related to configuring the thread pool size in the
> servicemix.xml file. I've done the following which works great with the
> servicemix-bean component:
> <property name="configs">
> <map>
> <entry key="flow.seda.servicemix-bean">
> <bean
> class="org.apache.servicemix.executors.impl.ExecutorConfig">
> <property name="corePoolSize" value="2"/>
> <property name="maximumPoolSize" value="3"/>
> <property name="queueSize" value="-1"/>
> </bean>
> </entry>
> </map>
> </property>
>
> The problem I'm trying to solve next is to understand if there's a way to
> set the thread pool at a more granular level - basically at the bean level
> that represents my endpoint. I need to be able to throttle specific end
> points that I've created with the servicemix-bean component.
>
> Is there a way to do this with a different thread pool setting? Or perhaps
> another strategy?
The granularity of the thread pools in ServiceMix only goes down to
the component level, not down to the service or endpoint level. For
example, the thread pool configuration you pasted above is for use
with the servicemix-bean component specifically within a SEDA flow
(i.e., to a component within a flow). That's the finest level of
granularity offered currently. If you need to throttle messages to
particular services or endpoints, you'll have to do so manually
through some other component.
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 Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
