On Fri, Oct 9, 2009 at 12:41 AM, erh <[email protected]> wrote: > > > > erh wrote: >> >> Well, I guess I actually *didn't* try w/o transferExchange param present >> at all before. oops. If I remove that, things work ok, at least with a >> seda queue. I'm trying it with an activemq queue now. >> > > yep, it works fine with an activemq too. I looked at the jms page again > (http://camel.apache.org/jms.html) and it clearly says that transferExchange > is for Camel 2.0 only. I have no idea how I missed that before. :( Oh > well, at least I got it working now. > > The DeadLetterChannel code looks like it got refactored for Camel 2.0, and > I'm not setup to test things against 2.0, so I don't know if it would > swallow exceptions the same way 1.6.2 does. >
Yeah error handling had a major overhaul in 2.0. But glad you got it working. However we may need to look into the issue you had with a mistyped URI for the DLC endpoint. Maybe Camel should pre check that on startup. So any misconfiguration is thrown on startup. > eric > -- > View this message in context: > http://www.nabble.com/dead-letter-channel-never-delivered-to-the-uri-tp25756520p25812863.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
