I have this configuration for component thread pools
<sm:executorFactory>
<bean
class="org.apache.servicemix.executors.impl.ExecutorFactoryImpl">
<property name="defaultConfig">
<bean
class="org.apache.servicemix.executors.impl.ExecutorConfig">
<property name="corePoolSize" value="100"/>
<property name="maximumPoolSize" value="-1"/>
<property name="queueSize" value="-1"/>
</bean>
</property>
<property name="configs">
<map>
<entry key="flow.jms.servicemix-jms">
<bean
class="org.apache.servicemix.executors.impl.ExecutorConfig">
<property name="corePoolSize" value="64"/>
<property name="maximumPoolSize" value="-1"/>
<property name="queueSize" value="2048"/>
</bean>
</entry>
<entry key="flow.seda.servicemix-bean">
<bean
class="org.apache.servicemix.executors.impl.ExecutorConfig">
<property name="corePoolSize" value="32"/>
<property name="maximumPoolSize" value="-1"/>
<property name="queueSize" value="1024"/>
</bean>
</entry>
</map>
</property>
</bean>
</sm:executorFactory>
Using this configuration, I am pushing in 1499 orders to be published to a
topic, but after processing 1124 orders, it stops and nothing is getting
published. It looks to me that the thread pool is exhausted.
When I look into the component statistics using JConsole, for the
servicemix-jms these statistics
inBoundExchangeCount = 1124
inBoundQueueSize = 0
outboundExchangeCount = 1499
Further looking into the SedaQueue for servicemix-jms component, it looks to
have taken thread pool configuration correctly
capacity = 2147483647
size = 375 (the messages count not yet published)
Please help me understand what am I doing wrong. I am using servicemix 3.3.1
with 2009.01 components.
Regards
Subh
--
View this message in context:
http://old.nabble.com/Configuring-Thread-pool-tp28005442p28005442.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
