Re: Camel Endpoint / Consumer startup

We can force camel to start the connection when the consumer is stared, it can fix the issue that you hit. BTW, the patch is on the way, please keep an eye on the JIRA comments :) -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://j

Re: ProducerTemplate without using Spring

Hi Lucas, This is correct. Here is a unit test part of the camel project where you can see that we support 2 options (using @Produce annotation or @Inject @Uri) https://github.com/apache/camel/blob/master/components/camel-cdi/src/test/java/org/apache/camel/cdi/ProduceInjectTest.java https://githu

Re: Not all processors are listed in JMX, preventing detailed route statistics/profiling

I've seen issues like this in HawtIO, and it's actually a Jolokia issue. Basically, Jolokia will only fetch the first N elements (unsorted, I believe) from the server, and if your MBean isn't one of those N, then... bugger? The solution is to go into HawtIO / Preferences / Jolokia, and change Max

Re: Camel Endpoint / Consumer startup

Hi, If the from("mqtt") component is not able yo establish a connection from the broker, then no apache camel exchange will be created. The issue could be if the .to("mqtt') producer tries to publish a message to a broker using the mqtt protocol. You can imagine to intercept the exception (due to

Re: Question about the message group

If your one thread process is no-blocked, you won’t hit the performance issue. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On October 16, 2014 at 9:21:44 PM, si

ActiveMQ InOut JMS messaging with external system

Hi Everyone, I have a route where the final destination is: activemq:queue:soapRequestQ?exchangePattern=InOut&asyncConsumer=true&useMessageIDAsCorrelationID=false&replyTo=responseQ&replyToType=Shared&requestTimeout=3&transacted=false In another route I have following configuration:

Camel Endpoint / Consumer startup

I've run into this issue with the MQTTEndpoint where the MQTT endpoint is started (causing the MQTT connection to be established). As a result, the flow of mqtt messages is started *before* any consumers of that endpoint are registered. This puts the guaranteed delivery aspect of MQTT quality of s

Not all processors are listed in JMX, preventing detailed route statistics/profiling

I have a webapp using Camel (v2.13.2) about to go into production, at the point of trying to tune things for performance. I'm having an issue with getting detail statistics for some routes, though. I'm using Hawtio 1.2, and for some routes, Hawtio is displaying the statistics for each processor i

Re: ProducerTemplate without using Spring

I'm using the camel-cdi component to inject ProducerTemplates into my EJB's e.g. @Inject @Uri("jms:ToolQueue?preserveMessageQos=true") ProducerTemplate toolQueueMessageProducer; My understanding is that the camel-cdi component should manage the look up and lifecycle of the producer te

Re: onException and doTry

A little further digging. I added some debugging output to incrementRedeliveryCounter and found the CamelRedeliveryCounter header is missing on the redelivery attempt, I see the following: 2014-10-16 09:01:48,976 [CamelJettyClient(0x106898e3)-88] DEBUG camel.processor.RedeliveryErrorHandler in in

Re: Question about the message group

only one consumer will affect performance. Do you have any other good solution? -- View this message in context: http://camel.465427.n5.nabble.com/Question-about-the-message-group-tp5757580p5757622.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: onException and doTry

I added some debugging output into RedeliveryPolicy.java and confirmed that it's not correctly incrementing redeliveryCounter. 2014-10-16 08:29:16,280 [CamelJettyClient(0x533bbc89)-59] DEBUG camel.processor.RedeliveryPolicy in shouldRedeliver, *redeliveryCounter = 1* 2014-10-16 08:29:16,280 [Came

Re: onException and doTry

Thanks Charles. I have a doTry inside route2 that has handled=false, and the *onException in route1 is firing the redelivery*. The only issue I have is that it redelivers an infinite number of times until the route succeeds instead of twice. It appears to be *forgetting the current retry count

Re: onException and doTry

Hi Nathan, When you use the doTry, doCatch processors, they will handle the exceptions instead of the interceptor (= onException). Regards, On Wed, Oct 15, 2014 at 9:36 PM, nathanwray wrote: > Hi all; > > I have a global onException defined that I hoped would let me retry an > entire route tw