Hi I have created a ticket https://issues.apache.org/activemq/browse/CAMEL-2063
To improve this so Camel reports a problem on startup if you have misconfigured the DLC endpoint. On Fri, Oct 9, 2009 at 12:18 AM, erh <[email protected]> wrote: > > > erh wrote: >> >> I got rid of *all* JMS options. The DLC queue is "seda:errorQ". The >> "from" endpoints are directories (<from uri="file:data/input"/>) (which >> causes OverlappingFileLockException and "Can not rename file..." errors, >> but that's probably a different problem). >> I tried with and without transferExchange present, and with it set to both >> true and false. >> > > 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. > > It looks like the problem is that a ResolveEndpointFailedException gets > thrown, complaining about the extra parameter ("There are 1 parameters that > couldn't be set on the endpoint"), but that exception gets replaced with the > original one when restoreExceptionOnExchange() is called > (DeadLetterChannel.java:328). If an exception is replaced like that, it > should probably be logged, but I don't know where the right place to do that > is. Maybe in restoreExceptionOnExchange()? > > eric > -- > View this message in context: > http://www.nabble.com/dead-letter-channel-never-delivered-to-the-uri-tp25756520p25812586.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
