[
https://issues.apache.org/jira/browse/CAMEL-26640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138847#comment-18138847
]
Guillaume Nodet commented on CAMEL-26640:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
The bug has been confirmed by code analysis: when stream caching is enabled at
route level and the message body is spooled to a file (FileInputStreamCache),
the advice ordering on the route internal processor causes
UnitOfWorkProcessorAdvice.after() to run before StreamCachingAdvice.after().
The UoW completion deletes the spool file via TempFileManager, then
StreamCachingAdvice.after() tries to reset the stream cache and fails with
"Cannot reset stream from file" because the file no longer exists.
A fix will be implemented and a PR opened shortly.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> Route level StreamCachingAdvice fails exchange with "Cannot reset stream from
> file" when using spooled stream cache
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-26640
> URL: https://issues.apache.org/jira/browse/CAMEL-26640
> Project: Camel
> Issue Type: Bug
> Components: came-core
> Affects Versions: 4.18.5, 4.22.1, 4.22.2, 4.23.0
> Reporter: Anton Berzelius
> Assignee: Guillaume Nodet
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
