Refers to a custom Thread Pool to be used for parallel processing. Notice if you
set this option then parallel processing is automatic implied and you do not
have to enable that option as well.

Sets the id of this node

Uses the Processor when preparing the org.apache.camel.Exchange to be send. This
can be used to deep-clone messages that should be send or any custom logic
needed before the exchange is send.

If enabled then the aggregate method on AggregationStrategy can be called
concurrently. Notice that this would require the implementation of
AggregationStrategy to be implemented as thread-safe. By default this is false
meaning that Camel synchronizes the call to the aggregate method. Though in some
use-cases this can be used to archive higher performance when the
AggregationStrategy is implemented as thread-safe.

If enabled then sending messages to the multicasts occurs concurrently. Note the
caller thread will still wait until all messages has been fully processed before
it continues. Its only the sending and processing the replies from the
multicasts which happens concurrently.

Shares the org.apache.camel.spi.UnitOfWork with the parent and each of the sub
messages. Multicast will by default not share unit of work between the parent
exchange and each multicasted exchange. This means each sub exchange has its own
individual unit of work.

Will now stop further processing if an exception or failure occurred during
processing of an org.apache.camel.Exchange and the caused exception will be
thrown. Will also stop if processing the exchange failed (has a fault message)
or an exception was thrown and handled by the error handler (such as using
onException). In all situations the multicast will stop further processing. This
is the same behavior as in pipeline which is used by the routing engine. The
default behavior is to not stop but continue processing till the end

If this option is false then the aggregate method is not used if there was no
data to enrich. If this option is true then null values is used as the
oldExchange (when no data to enrich) when using POJOs as the AggregationStrategy

This option can be used to explicit declare the method name to use when using
POJOs as the AggregationStrategy.

Refers to an AggregationStrategy to be used to assemble the replies from the
multicasts into a single outgoing message from the Multicast. By default Camel
will use the last reply as the outgoing message. You can also use a POJO as the
AggregationStrategy

If enabled then Camel will process replies out-of-order eg in the order they
come back. If disabled Camel will process replies in the same order as defined
by the multicast.

Sets a total timeout specified in millis when using parallel processing. If the
Multicast hasn't been able to send and process all replies within the given
timeframe then the timeout triggers and the Multicast breaks out and continues.
Notice if you provide a TimeoutAwareAggregationStrategy then the timeout method
is invoked before breaking out. If the timeout is reached with running tasks
still remaining certain tasks for which it is difficult for Camel to shut down
in a graceful manner may continue to run. So use this option with a bit of care.