I have a Camel route that consumes from *netty:udp* and uses the *multicast() *DSL method to multicast to several different destinations (i.e. Camel throughput logger, local backup file, a SEDA queue that produces to Kafka, and another SEDA queue on a route that contains a UdpAckBack processor that composes an ack for each received UDP datagram). I'm having trouble getting the UDP acks to be sent back to the UDP client. Yes, I know that you don't typically acknowledge received UDP datagrams, but I have a requirement to optionally do so.
I'm trying to use an *AggregationStrategy* so that the processed exchange from the multicast destination containing the UdpAckBack processor is sent back as the ack to each of the received UDP datagrams. Additionally, I have to honor an application configuration setting that says whether or not to send UDP acks, so in some cases I'll need to multicast to the above destinations, but with no UDP acks sent back to the UDP client. So my question is, can an *AggregationStrategy* be configured so that it either sends back the result of a particular multicast destination as the UDP ack, and also be setup so that, when configured, no multicast response is sent? I'm kind of stuck with how to implement this kind of aggregation strategy. Maybe I could have the route that contains the UdpAckBack processor set a custom Exchange header that could be examined in the *aggregate(Exchange exchange1, Exchange exchange2) *method? Any help is greatly appreciated!!! Thanks, Steve -- View this message in context: http://camel.465427.n5.nabble.com/Camel-multicast-with-aggregationStrategy-tp5770505.html Sent from the Camel - Users mailing list archive at Nabble.com.
