This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

  Apache ServiceMix NMR #usernavbar() #printableicon() #pdficon() #feedicon()  
When you contribute content to this Wiki, you grant a license to the ASF for inclusion in ASF works (as per the Apache Software License).
  13. Clustering
Skip to end of metadata
Go to start of metadata

13. Clustering

The clustering mechanism uses JMS to provide distribution and fail-over on multiple JBI containers.


  • transparent remoting
  • rollback and redelivery when a JBI exchange fail
  • load balancing among JBI containers able to handle a given exchange
  • pause new exchanges processing when the number of concurrently processed messages reach a given threshold


The JBI cluster engine is not installed by default in ServiceMix NMR. The main reason is that it requires a JMS broker to be available and none is included inside the distribution.

Using ActiveMQ

If you plan to use ActiveMQ (which is recommended), you can use the following configuration to create the cluster engine:

    <bean id="clusterEngine" class="org.apache.servicemix.jbi.cluster.engine.ClusterEngine">
        <property name="pool">
            <bean class="org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool">
                <property name="connectionFactory" ref="connectionFactory" />
                <property name="destinationName" value="${destinationName}" />
        <property name="name" value="${clusterName}" />

    <osgi:list id="clusterRegistrations"
       <osgi:listener ref="clusterEngine" bind-method="register" unbind-method="unregister" />

    <osgi:reference id="connectionFactory" interface="javax.jms.ConnectionFactory" />

    <osgi:service ref="clusterEngine">
            <entry key="NAME" value="${clusterName}" />

    <osgix:cm-properties id="clusterProps" persistent-id="org.apache.servicemix.jbi.cluster.config">
        <prop key="clusterName">${}</prop>
        <prop key="destinationName">org.apache.servicemix.jbi.cluster</prop>

    <ctx:property-placeholder properties-ref="clusterProps" />

This configuration is the default one for ActiveMQ and is provided inside an OSGi bundle. It will use a JMS ConnectionFactory retrieved from OSGi.

If you want to use this default configuration, a simple way to create and configure the cluster engine is to drop a feature descriptor in the deploy folder of your ServiceMix NMR / Kernel:

    <feature name="cluster-example-smx2">
        <config name="org.apache.servicemix.jbi.cluster.config">

This will install the activemq and jbi-cluster feature. Note that the cluster engine will not be started until a JMS ConnectionFactory is available from the OSGi registry, which can be done easily by creating an ActiveMQ broker using the following command:

smx@root:/> activemq/create-broker

The default configuration for the created broker will include a JMS ConnectionFactory definition and register it in the OSGi registry.

Note about using a network of brokers

Internally, the JBI clustering engine makes use of message selectors to allow cluster members to pick messages of the queue. When using an ActiveMQ Network of Brokers , you have to add conduitSubscriptions="false" to the network connector configuration.

Using another JMS Broker

The cluster engine, though optimized for using ActiveMQ, can be used with any JMS compliant broker. In order to do so, you need to modify the above configuration to not use the ActiveMQ optimized requestor pool:

    <bean id="clusterEngine" class="org.apache.servicemix.jbi.cluster.engine.ClusterEngine">
        <property name="pool">
            <bean class="org.apache.servicemix.jbi.cluster.requestor.GenericJmsRequestorPool">
                <property name="connectionFactory" ref="connectionFactory" />
                <property name="destinationName" value="${destinationName}" />
        <property name="name" value="${clusterName}" />

You also need to create a JMS ConnectionFactory pointing to your JMS broker and register it in OSGi, or put its definition directly in the JBI cluster engine Spring configuration file.


When using an OSGi packaged JBI Service Assemby, you can include the clustered endpoints definitions in the spring configuration file directly.

<http:consumer-endpoint id="myHttpConsumer" service="test:myService" endpoint="myEndpoint" />

<bean class="org.apache.servicemix.jbi.cluster.engine.OsgiSimpleClusterRegistration">
  <property name="endpoint" ref="myHttpConsumer" />

When using a JBI packaged Service Assembly, you need to create a spring application to register the endpoint as a clustered endpoint:

<bean class="org.apache.servicemix.jbi.cluster.engine.OsgiSimpleClusterRegistration">
  <property name="serviceName" value="test:myService" />
  <property name="endpointName" value="myEndpoint" />


  • No labels