camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Geer <>
Subject RecipientList Component Resolution
Date Tue, 28 Apr 2015 04:36:28 GMT
I’ve run into a strange situation while using the RecipientList EIP. We are running Camel
inside Karaf and defining CamelContexts in blueprint files. We have two Karaf containers.
The first one runs Bundle A and the second one runs ActiveMQ (simplified for example purposes).
In the blueprint file for Bundle A we define the ActiveMQ component like this.

    <bean id="producerActivemqConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="brokerURL" value="tcp://serverB:61616?trace=false&amp;soTimeout=60000&amp;connectionTimeout=60000"

    <bean id="producerPooledConnectionFactory" class="org.apache.activemq.pool.PooledConnectionFactory"
init-method="start" destroy-method="stop">
        <property name="maxConnections" value="4" />
        <property name="connectionFactory" ref="producerActivemqConnectionFactory" />

    <bean id="activemq" class="org.apache.activemq.camel.component.ActiveMQComponent">
        <property name="connectionFactory" ref="producerPooledConnectionFactory"/>
        <property name="transacted" value="false"/>
        <property name="cacheLevelName" value="CACHE_NONE"/>

If we were defined out Camel Route like this, everything works properly and the message gets
sent to the AMQ server on Server B.

    <camel:camelContext id=“ctx" trace="false">
            <camel:from uri="direct:ingest"/>
            <camel:to uri=“activemq:queue:ingest.client”/>

But if we use the recipient list EIP like below it resolves the activemq component to the
base one and we receive the error message listed below.

    <camel:camelContext id=“ctx" trace="false">
            <camel:from uri="direct:ingest"/>

WARN  | ActiveMQ Task-1  | FailoverTransport                | 146 - org.apache.activemq.activemq-osgi
- 5.10.2 | Failed to connect to [tcp://localhost:61616] after: 80 attempt(s) continuing to

Does the ReceipientList processor resolve components differently than everything else?

View raw message