Thanks Claus, will do it. I was wondering if the redelivery was a camel feature (independent of endpoint) for instance, if I configure it to 5 redeliveries on a file endpoint, it would try 5 times before failing, did I get this wrong?
Also, using the Pojo annotations is it possible to use more advanced features such the ones that we have on routes? Like filters for instance. Regards On Mon, Jul 25, 2011 at 4:36 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Mon, Jul 25, 2011 at 4:05 PM, Vinicius Carvalho > <java.vinic...@gmail.com> wrote: > > Hi there! I'm producing and consuming messages using camel pojo. > > > > So far so good but I need to configure the TransactionErrorHandler ( > > http://camel.apache.org/transactionerrorhandler.html) for my MDBs for > > instance: > > > > @Consume(uri="jms:queue:testQueue?transacted=true") > > > > > > How do I change the behavior of the redelivery policy for it? I'd like to > > use a DLQ with 3 attempts for instance. > > > > If you use transacted acknowledge mode, then its the JMS broker that > handles redelivery and dead letter queues. > So check your message broker how to configure and use that. > > For ActiveMQ there is some details here > http://activemq.apache.org/redelivery-policy.html > http://activemq.apache.org/message-redelivery-and-dlq-handling.html > > > Regards > > > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/ >
