I have context level defined error handling (retry interval and retry
attempts defined) that I am trying to test out. Yet it will never be
invoked no matter how I simulate the error with mock end points. Does
anyone how this can work?
Given my route I'm testing just looks like:
from(myQueue).to
Hi all,
Does anyone know how to properly implement redelivery that does not block
normal processing of other messages?
I have an error handler defined with DLQ, but once that kicks in, no
messages will be consumed.
I know about asyncConsumer, I set it on the JmsConfiguration but to no
avail. On
By the way, I am using Camel 2.11.1 and also in my error handler I made sure
I use asyncDelayedRedelivery. So everything seems to be in order, yet I
cannot get the redelivery to be fully async
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-JMS-redelivery-blocks-normal
I am using v2.10.3.
I am writing an integration test and need to simulate a database exception
after consuming from a JMS queue like so:
from("jms:testQueue").to("mock:test");
mockTest.whenAnyExchangeReceived(new Processor() {
public void process(final Exchange exchange) throws Exception {
This is great for creating coarse grained expectations on routes, but I am
struggling with the documentation.
Hoping the experts can help me answer the questions, based on the given
example:
from(direct:hello).process().to(direct:foo)
from(direct:foo).process().to(direct:bar)
from(direct:bar).m
