camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Retroactive message routing possible ?
Date Wed, 28 Nov 2012 08:30:57 GMT
On Mon, Nov 26, 2012 at 5:52 PM, c031917 <peter.marx@knorr-bremse.com> wrote:
> 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:route>
>                     <camel:from uri="activemq:topic:blah" />
>             <camel:to uri="file:/opt/blah" />
>         </camel:route>
>
> 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 ?
>

Do you have durable subscribers on these topics? They would need to be that,
so they can receive messages that was sent to the topic while they were offline.



>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Retroactive-message-routing-possible-tp5723249.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
View raw message