camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c031917 <>
Subject Retroactive message routing possible ?
Date Mon, 26 Nov 2012 16:52:38 GMT
I have two AMQ brokers A and B, duplex & statically connected, like the
supermarket example in AMQ in action, Chapter 10.

Broker B is embedded in Camel to implement routing by pure configuration.
Broker A runs standalone.

A Java producer on A is feeding messages to a topic.

They are delivered and processed 100% by the route on B-side, as long as
connection A-B is up:

		    <camel:from uri="activemq:topic:blah" />
            <camel:to uri="file:/opt/blah" />

But when connection between A and B is interrupted, messages on A are piling
up and after
reconnection they remain on A. Only fresh messages created after reconnect
are sent from A to B.

Where do i have to add an option so that all messages are delivered from A
to B ? 

In other words - how can i get retroactive behaviour with Camel ? 

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message