Pratibha,
Actually, I thought that -1 wasn't supported at all but in fact it is
and it should have worked. What I was trying to say: if you really want
to redeliver an infinite number of times, you can just as well drop the
deadLetterChannel alltogether and write
from(SERVICE_IN).errorHandler(noErrorHandler).to(BEAN_IN)
instead and have ServiceMix take care of retrying by never taking the
message off the SERVICE_IN queue.
Gert
pratibhaG wrote:
may I ask you to please clarify this point.
"If you specify noErrorHandler, the JMS endpoint in ServiceMix will just
receive your bean exception and will not acknowledge the message off the
queue. This will cause it to retry it forever. For more QoS, you can
use transactions on the JBI JMS endpoint (or use Spring transactions
with the Camel JMS endpoints). "
If I put
from(SERVICE_IN).errorHandler(deadLetterChannel(ERROR_IN).maximumRedeliveries(2)).to(BEAN_IN);
it works fine. Here I am doing the same thing first specify a dead letter
queue and afterwards specify redelivery.
Thanks,
Pratibha
pratibhaG wrote:
Is this feature also available if I use camel in servicemix? That is if I
use
servicemix-camel component and have configuration like this:
from(SERVICE_IN).errorHandler(deadLetterChannel(ERROR_IN).maximumRedeliveries(-1)).to(BEAN_IN);
will my message be redelivered infinitely if it gets error every time it
tries to redelive?
I tried this in servicemix 3.2.1 but it never tried to redeliver my
message.
It has the same behaviour as of maximumRedeliveries(0).
Any idea?
Regards,
Pratibha
-----
---
Gert Vanthienen
http://www.anova.be
