[
https://issues.apache.org/jira/browse/CAMEL-6991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829793#comment-13829793
]
Claus Ibsen commented on CAMEL-6991:
------------------------------------
Ah use Camel 2.12 onwards as Jetty ends the UoW after it has written the
response. So the cleanup of the file happens afterwards now.
For earlier releases use .convertBodyTo(byte[].class) to ensure the content is
in-memory, at the end of the jetty route.
> Problem with stream caching and DefaultHttpBinding.writeResponse
> ----------------------------------------------------------------
>
> Key: CAMEL-6991
> URL: https://issues.apache.org/jira/browse/CAMEL-6991
> Project: Camel
> Issue Type: Bug
> Components: camel-http
> Affects Versions: 2.11.2
> Environment: Debian 7
> Reporter: Ulrich Kramer
> Fix For: 2.12.0
>
>
> DefaultHttpBinding.writeResponse was modified between 2.11.0 and 2.11.2. This
> yields to a problem with stream caching.
> When exchange.out is not set target (DefaultHttpBinding.java:215) is
> assigned to exchange.in . exchange.in may contain a body which is already
> removed by an onCompletion callback. In DefaultHttpBindung.java:377 this body
> is read. This may yield to an exception
--
This message was sent by Atlassian JIRA
(v6.1#6144)
