I would like to clarify something regarding Camel exeption handling....
>From the IBM manuals:
"The WebSphere® MQ queue manager keeps a record of the number of times that
each message has been backed out. When this number reaches a configurable
threshold value, the message consumer requeues the message to a named
backout queue. If this re-queuing fails for any reason, the message is
removed from the input queue and either requeued to the dead-letter queue,
or discarded."
So the question is whether this automagical message consumer is (or can be)
mimicked in Camel?
The advantage here is that I could treat AMQ and MQSeries in the same way
for exception processing that is I could rely on the underlying JMS provider
to deal with poison (badly formatted) messages.
Is this is what's happening if I say:
onException(MQException.class)
.maximumRedeliveries(5)
.to("mq:requeueName");
Thanks in advance for your support.
Best regards
Ray
--
View this message in context:
http://camel.465427.n5.nabble.com/hanlding-poison-messages-from-IBM-MQ-Series-tp5056027p5056027.html
Sent from the Camel - Users mailing list archive at Nabble.com.
