Avoiding duplicate messages

Hi guys, consider the following route: from(srcEndpoint). to(destEndpoint1). to(destEndpoint2) I have a Java program which does the following: - create a Camel exchange, add an onComplition action to remove the exchange from the cache on success, store the exchange in a cache, and then send it t

Re: Oncompletion callbacks and message history of Camel exchanges

Hi again, Did someone from the Camel experts have time to look at my questions above? Thanks. Best regards, Atanas -- View this message in context: http://camel.465427.n5.nabble.com/Oncompletion-callbacks-and-message-history-of-Camel-exchanges-tp5744543p5744927.html Sent from the Camel - User

Oncompletion callbacks and message history of Camel exchanges

Hi guys, I want to store exchanges in a cache before processing them with Camel routes. Consider the following route: from(vm) .to(file) .to(jms); My emitter application performs the following operations: 1. store exchange in cache 2. Add oncompletion callback 3. send exchange to vm (the Camel r

Re: Persist headers when using cache

I don't think that the persistence configuration influences how the cache component writes the exchanges into the cache. When performing add or update operations, the *org.apache.camel.component.cache.CacheProducer* class uses its createElementFromBody() method which takes the in message body from

Usage of Camel cache component (Camel component auto discovery)

Hi guys, I’ve looked through many Camel sources (Camel in Action, Camel documentation for components on the net) but did not manage to solve the following problem. I'm trying to deploy a route which uses the camel-cache component, however, I'm getting the well-known org.apache.camel.ResolveEndpoi

Re: Change ErrorHandlerFactory of a route runtime

Hi Claus, Thanks for the quick answer. I'll give it a try with the JMX proposal . . . Regards, Atanas -- View this message in context: http://camel.465427.n5.nabble.com/Change-ErrorHandlerFactory-of-a-route-runtime-tp5730057p5730072.html Sent from the Camel - Users mailing list archive at Nab

Change ErrorHandlerFactory of a route runtime

Hello, is Camel capable of the following: I have a CamelContext with several routes defined and running. I have specified an ErrorHandlerFactory in the CamelContext (e.g. a DefautlErrorHandlerBuilder with maximumRedeliveries, redeliveryProcessor, and redeliverDelay properties defined) so that all

ErrorHandling support for asynchronous JMS producers

Hi all, Does Camel provide error handling support for MessageProducer.send invocations that behave *asynchronously*? For example, lets have a look at the the following route: *from(endpoint).errorHandler(errorHandlerFactory).to(jms:topic:myTopicName)* We assume that the topic myTopicName does not

Re: How does a Camel component update change existing routes

. If I create a new producerTemplate after the restart everything is ok. I will try with restarting the template because creating a new each time is quite expensive. On Fri, Sep 14, 2012 at 9:07 AM, Claus Ibsen-2 [via Camel] < ml-node+s465427n5719338...@n5.nabble.com> wrote: > On Thu, Sep

Re: How does a Camel component update change existing routes

So, I have two types of routes: 1) from vm:... to jms:topic.. 2) from jms:topic... to user processor I've tried restarting the routes while changing the component - after that the second type of routes still consume from the old jms provider ... and these consuming from vm don't work at all But I

Re: How does a Camel component update change existing routes

Thanks for the prompt reply! Just to clarify: shutting down all the routes will not require a camelcontext restart? So, I have to options: 1) Stop all routes -> shutdown old component -> add new component -> start new component -> start all routes 2) Stop context -> shutdown old component -> add

How does a Camel component update change existing routes

Hello, I'm using the JMS Component to create a JMS application which have to types of toutes: 1) from vm IM endpoints to JMS topics. 2) from JMS topics to user processors. The JMS Component uses JNDI for topic/connection factory resolution. And I want to change the physical data of this component

Re: Routing from non existing JMS topics

n5.nabble.com> wrote: > Related to - > > http://camel.465427.n5.nabble.com/NEWBIE-automatic-queues-creation-td5106080.html#a5106890 > > Thanks. > Regards, > Narita > > -Original Message- > From: shindito [mailto:[hidden > email]<http://user/SendEmail

Routing from non existing JMS topics

Hello all, As you know, ActiveMQ supports the following functionality: If a client subscribes to a topic that currently does not exists on the JMS provider, then this topic is automatically created and bound to the JMS provider. However, the JMS provider that we currently use, does not support th