Thanks for the reply; so explicit routing back to the dynamic router should
be avoided, is that what you're saying? This would probably explain why I'm
seeing duplicate debugging output.
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-Router-forwarding-and-tracking-
Oh I see.
Yes I know that ActiveMQ can do that. WebSphere does support it too, but to
a lesser extend than ActiveMQ. If WebSphere does not signal to the client
that a reconnect is allowed, the client is going to crash.
Anyway...
Is it possible that Apache Camel is the greatest Library ever created
I logged a ticket to improve sjms-batch. However for sjms its more
tricky. And also mind that each JMS client may have their own error
handling / failover et all.
https://issues.apache.org/jira/browse/CAMEL-10615
On Sat, Dec 17, 2016 at 4:03 PM, Claus Ibsen wrote:
> Not all components support the
Not all components support the bridge error handler.
As said its component specific, and some special ones like the JMS
based do not as they have their own JMS client code / logic and how
errors is dealt with.
Often they have failover / retry options in the JMS client, eg
ActiveMQ has some specia
So I went back and read the book again, but it does not show how to handle
exception outside of the routing engine. I check the file consumer example
and tried to apply it, but it did not work. This is what I did:
/onException(classOf[Exception]).to("log:was-caught ${body}")
from("batch-sjms:test
