Side effects on payload changes with Camel Splitter and Multicast

Solution Verified - Updated -

Issue

  • Camel always creates shallow copies of the original Exchange by design, even with parallel processing
  • Every change made to the Exchange's payload is visible and can have side effects in the following processing

Environment

  • Red Hat Fuse (Fuse)
    • 6
    • 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.