[
https://issues.apache.org/jira/browse/CAMEL-22414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18020748#comment-18020748
]
John Yin commented on CAMEL-22414:
----------------------------------
Hi [~davsclaus],
Our application was just trying to call a remote HTTP server and process its
response. I put together a small project (attached) by modifying the
Camel-Spring-Boot example (rest-cxf) project. It sends a GET to google.com
(\camel-spring-boot-examples-latest\rest-cxf\src\main\groovy\org\apache\camel\example\springboot\cxf\CamelRouterGroovy.groovy).
If the project uses Camel 4.14.0, it will generate a stream closed exception.
If it switches to use Camel 4.10.6, it will work fine. Please let me know if
you need more information. Thanks in advance for looking into this.
Thanks,
John
> In 4.14.0, after calling CXF HTTP, the response stream is not cached
> --------------------------------------------------------------------
>
> Key: CAMEL-22414
> URL: https://issues.apache.org/jira/browse/CAMEL-22414
> Project: Camel
> Issue Type: Bug
> Components: came-cxf
> Affects Versions: 4.14.0
> Reporter: John Yin
> Priority: Minor
> Attachments: camel-spring-boot-examples-latest.zip
>
>
> After migrating from 4.10.6 -> 4.14.0, the response of our CXF HTTP call is
> not stream cached. When we tried to read the response the second time, it
> became empty. The Camel stream caching is enabled. While we could do a
> convertBody() to reset the response to String, but we would have to add such
> conversion in exception handling as well and may not be bullet proof. We did
> not have this issue in 4.10.6. We use CXF 4.1.3 with hc5. Any idea?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
