camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kemal Bayram <kemal.bay...@inmarsat.com>
Subject No consumers available on endpoint issue
Date Mon, 23 Mar 2015 14:05:39 GMT
Hi,
I have two camel contexts that have a routing between them via direct-vm:

Context 1:

    <route>
        <from uri="input:queue:internal"/>
        <to uri="bean:setDest"/>
        <recipientList parallelProcessing="true"
ignoreInvalidEndpoints="true" streaming="true">
            <property>destination</property>
        </recipientList>
    </route>

Context 2:

    <route>
        <from uri="direct-vm:1208:queue:internal"/>
        <setProperty propertyName="destination">
            <xpath resultType="java.lang.String">name(/*)</xpath>
        </setProperty>
        <recipientList>
            <simple>direct:${property.destination}</simple>
        </recipientList>
    </route>

    <route>
        <from uri="direct:element"/>
        ...
    </route>

The first route uses a bean that sets a destination property that is used by
recipient list to forward it onto the second route in the other context via
direct-vm.  The second route then extracts the XML root element name and
sets that as a property that is then used as the destination to another
route in the same context via direct.

This set up works nicely however if I change the communication between the
contexts from direct-vm to vm the recipientList in the second route fails
with "No consumers available on endpoint: Endpoint[direct://record]" even
though the endpoint is there and works fine with direct-vm.

Am I missing something obvious?

Thanks in advance
Kemal



--
View this message in context: http://camel.465427.n5.nabble.com/No-consumers-available-on-endpoint-issue-tp5764653.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message