Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Each thread pool has its own identifier, for example:

  • Wiki Markup
    {{component.\[id\]}} where {{\[id\]}} is the name of the component
  • Wiki Markup
    {{flow.seda.\[id\]}} where {{\[id\]}} is the name of the component
  • Wiki Markup
    {{flow.jca.\[destination\]}} where {{\[destination\]}} is the name of the JMS destination used

Thread pools are configured hierarchically using these ids. It means that when an executor is created with an id of <code>foo.bar</code>, the factory will look for a configuration in the following way:

...

Code Block
langxml
<sm:container ...>
  <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="4"/>
            <property name="maximumPoolSize" value="-1"/>
            <property name="queueSize" value="0"/>
          </bean>
      </property>
      <property name="configs">
        <map>
          <entry key="flowcomponent.sedaservicemix-http">
            <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>
          <entry key="flow.seda.myComponentcomponent.servicemix-jsr181">
            <bean class="org.apache.servicemix.executors.impl.ExecutorConfig">
              <property name="corePoolSize" value="2"/>
              <property name="maximumPoolSize" value="4"/>
              <property name="queueSize" value="-1"/>
            </bean>
          </entry>
        </map>
      </property>
    </bean>
  </sm:executorFactory>
  ...
</sm:container>

...