Camel's WireTap node supports two flavors when tapping an Exchange.
With the traditional Wire Tap, Camel will copy the original Exchange and set its Exchange Pattern to InOnly, as we want the tapped Exchange to be sent in a fire and forget style. The tapped Exchange is then sent in a separate thread so it can run in parallel with the original. Beware that only the Exchange is copied - Wire Tap won't do a deep clone (unless you specify a custom processor via onPrepareRef which does that). So all copies could share objects from the original Exchange.
Camel also provides an option of sending a new Exchange allowing you to populate it with new values. See the Camel Website for dynamically maintained examples of this pattern in use.