You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/11/21 21:04:35 UTC

[jira] [Commented] (CAMEL-6991) Problem with stream caching and DefaultHttpBinding.writeResponse

    [ https://issues.apache.org/jira/browse/CAMEL-6991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829284#comment-13829284 ] 

Claus Ibsen commented on CAMEL-6991:
------------------------------------

Are you talking about using onCompletion
http://camel.apache.org/oncompletion.html

eg onCompletion in a route, or what?

> 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
>
> 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)