Skip to content

CAMEL-24392: Fix BacklogTracerRouteAdvice draining WrappedFile streambody (backport 4.22.x) - #25504

Open
davsclaus wants to merge 1 commit into
camel-4.22.xfrom
backport/CAMEL-24392-4.22.x
Open

CAMEL-24392: Fix BacklogTracerRouteAdvice draining WrappedFile streambody (backport 4.22.x)#25504
davsclaus wants to merge 1 commit into
camel-4.22.xfrom
backport/CAMEL-24392-4.22.x

Conversation

@davsclaus

Copy link
Copy Markdown
Contributor

Summary

Backport of #25492 to camel-4.22.x.

  • Cache the stream in BacklogTracerRouteAdvice.before() when stream caching is enabled, so the body is converted to a re-readable StreamCache before the tracer reads it
  • Prevents SFTP streamDownload bodies from being drained by the backlog tracer

Cherry-picked cleanly from main (947aa5f).

Claude Code on behalf of davsclaus

🤖 Generated with Claude Code

…body

CAMEL-24392: Fix BacklogTracerRouteAdvice draining WrappedFile stream body

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@github-actions

Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@github-actions github-actions Bot added the core label Aug 14, 2026
@gansheer

Copy link
Copy Markdown
Contributor

@davsclaus Shouldn't the build run on 4.22 backport like for the 4.18 one?

@davsclaus

Copy link
Copy Markdown
Contributor Author

CI likely hasnt been setup for that, check the .github ci files - likely need to add 4.22.x branch somewhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants