If you use the Camel, you can configure the error handler to redeliver your message. The good is, Camel will only redeliver the failed endpoint. The bad is, the redelivery is done in memory. But if you use the TransactionalErrorHandler (which supports redelivery) you can make sure you will not lose the message, if some one kill your running process while redelivering.
Best, Christian On Tue, Nov 13, 2012 at 5:35 PM, dunnlow <dunn...@yahoo.com> wrote: > Hello, I am using camel 2.9 and Spring 3. I have a transacted route in > which > I am pulling messages from a queue (activemq) and sending messages to two > web services (via multicast). The web services are notification services > that send messages to users (there is no real roll back strategy - once the > notification is sent, it is sent). When I only needed to send to one > service, things worked fine; if the service couldn't be reached for some > reason, then the transacted route would keep resending until successful. > > The problem came up once I added a second web service. Now if one web > service fails, the retry goes back to both services so the working services > keeps sending out notifications until the one that isn't working gets > fixed. > Obviously, I'd like ONLY the broken service to keep retrying (pulling the > one that worked out of the transaction). > > Is there a good/standard way to handle this in camel? (Obviously I can > handle it myself outside camel, but am hoping for a camel/spring specific > solution) > > Thanks for any ideas, > -J > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Transacting-two-web-services-EIP-tp5722673.html > Sent from the Camel - Users mailing list archive at Nabble.com. > --
