Claus Ibsen created CAMEL-26157:
-----------------------------------
Summary: camel-reactive-streams - the producer leaves the
CamelReactiveStreamsCallback header (a lambda) on the message
Key: CAMEL-26157
URL: https://issues.apache.org/jira/browse/CAMEL-26157
Project: Camel
Issue Type: Bug
Components: camel-reactive-streams
Reporter: Claus Ibsen
Fix For: 4.24.0
Found while adding the catalog body types of xmpp, pubnub and reactive-streams
(CAMEL-24961, PR #28394).
h4. 1. The producer leaves its callback header on the message
{{ReactiveStreamsProducer.process}} (main 2a465aa4814c, line 44) stores its
dispatch callback in the {{CamelReactiveStreamsCallback}} header
({{ReactiveStreamsHelper.attachCallback}}, line 41) and never removes it, so
after {{to("reactive-streams:...")}} the message carries a header whose value
is a lambda. It shows up in logs, tracing and {{getHeaders()}}. Checked on
4.24.0-SNAPSHOT with the reactor engine.
Proposed: remove the header in the callback before {{callback.done}}
({{ReactiveStreamsHelper.detachCallback}}), or keep the callback in an exchange
property.
_Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
