I have an application that uses Camel 2.21.1 and Kafka 1.1
I had a bug where the deserializer for the consumer threw an exception when
deserializing the message. I could see an exception in the log, but the
consumer never handled the exception and the message was throwing an exception
each time
I am in the process of upgrading an application that uses Camel and Kafka
from Camel 2.18.2 to 21.1 and Kafka from 0.10.0.2 to 1.1.0
The Kafka upgrade just worked, however URL used by camel to specify the
kafka consumers and producers changed.
Old format:
kakfa:server.port?topic=mytopic&...
New
case was calling multicast in this way.
https://github.com/apache/camel/blob/master/camel-core/src/test/java/org/apache/camel/processor/MulticastParallelFailureEndpointTest.java
So why isn't multicast handling errors in a way consistent with other
components, and if this is by design could
I have a route that uses multicast parallel processing to process messages
in parallel. It works great, when everything is good. However if an
exception happens in any of the multicasted routes, the exception is
handled by the multicast but never written to the route's dead letter
channel. I am usi