What is the reasoning behind having the second consumer only process in the case of failover or slow processing?
If you could deploy multiple instances of the consumer, you’d get the throughput you’re after. Also, if you want to ensure that only one consumer is actively processing messages at any given time, you could use exclusive consumers (http://activemq.apache.org/exclusive-consumer.html <http://activemq.apache.org/exclusive-consumer.html> ). You can probably get the “slow processing” worked out using something similar to the example in the Camel ActiveMQ Broker Component documentation (http://activemq.apache.org/broker-camel-component.html <http://activemq.apache.org/broker-camel-component.html>). The example works on queue depth - I don’t know if that would work for you or not. > On Feb 22, 2016, at 10:32 AM, fliot <[email protected]> wrote: > > Thanks Quinn for your feedbac, > > Here is my test case, > > A single ActiveMQ broker, several Camel consumers, > And I want one of these consumer get messages without delay (letting him > consume messages before the others, and other acting in case of fail-over or > too long time for the first instance). > > Thanks in advance. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Activemq-initialDelay-tp5778033p5778067.html > Sent from the Camel - Users mailing list archive at Nabble.com.
