pache.org/error-handler.html .
eric
--
View this message in context:
http://www.nabble.com/dead-letter-channel-never-delivered-to-the-uri-tp25756520p25756520.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ainer-1][jms.listener.DefaultMessageListenerContainer(AbstractMessageListenerContainer)-handleListenerException(634)]:
> Execution of JMS message listener failed
> org.apache.camel.RuntimeCamelException: java.lang.Exception: test exception
> at
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamel
t's going wrong. (although given that I'm not
familiar with the internals of Camel it'll be a bit of a toss up as to
whether I'll be able to figure out anything useful)
eric
--
View this message in context:
http://www.nabble.com/dead-letter-channel-never-delivered-to-the-uri-tp25756520p25812190.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ionOnExchange() 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-lette
x27;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.
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.
d 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-lette
oreExceptionOnExchange() 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
