[
https://issues.apache.org/jira/browse/CAMEL-26132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136547#comment-18136547
]
Claus Ibsen commented on CAMEL-26132:
-------------------------------------
PR: https://github.com/apache/camel/pull/28908
On a clone failure the split consumer now fails the exchange
(RuntimeCamelException caused by the CloneNotSupportedException), keeps the
SyndEntry as the body and logs at WARN, so the route error handler gets the
entry instead of a null body.
_Claude Code on behalf of Claus Ibsen (davsclaus)_
> camel-rss - when cloning the SyndFeed fails, the split consumer sends an
> exchange with a null body
> --------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26132
> URL: https://issues.apache.org/jira/browse/CAMEL-26132
> Project: Camel
> Issue Type: Bug
> Components: camel-rss
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Found while adding the catalog body types of atom, rss, oaipmh and weather
> (CAMEL-24961, PR #28417).
> h4. 1. A failed clone sends a null body
> {{RssEndpoint.createExchange}} (main 2a465aa4814c, lines 78-82) clones the
> SyndFeed for each entry; when the clone fails with CloneNotSupportedException
> it only logs at debug level and sends the exchange with a null body, so the
> route gets an empty message and the entry is lost without a visible error.
> Read in the code, not run.
> Proposed: fail the exchange (or fall back to the entry itself) instead of
> sending a null body, and log at WARN.
> _Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
