You may treat the camel redeliver as a logic level configuration and ActiveMQ redeliver as transport level configuration. They should not affect each other. But if you want to dump the file, you need to consider to setup the camel redelivery policy of it.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Tuesday, December 11, 2012 at 6:25 AM, dunnlow wrote: > I'm using camel 10.0 and activemq 5.5. > > I currently have a redelivery policy currently configured on my > ConnectionFactory that is being used by my ActiveMQ component (using > org.apache.activemq.RedeliveryPolicy). However, what I really want to do is > set up redelivery in camel so that after the msg cannot be delivered for > several tries, it gets dumped out to a file (via xstream) and pulled off the > queue. > > I was reading about the org.apache.camel.builder.DeadLetterChannelBuilder, > and it sounds like what I want. I see how to configure the bean (passing, > in a dead letter uri and redelivery policy). Also, I see how to configure > the Camel redelivery policy, but I'm not sure how to integrate it into my > route consuming from activemq. > > Should I just remove the redelivery policy from my ConnectionFactory > configuration and set the errorHandlerRef on my route that consumes from > ActiveMQ to my Camel DeadLetterChannelBuilder bean? > > Thanks for any insight, > -J > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Using-Dead-letter-channel-with-ActiveMQ-tp5723865.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
