camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] [Updated] (CAMEL-5138) HTTP component always use a CachedOutputStream
Date Thu, 26 Apr 2012 15:28:17 GMT


Christian Schneider updated CAMEL-5138:

    Attachment: CAMEL-5138-1.patch

Removing the Caching and the releasing of the connection. If the inputstream is closed later
the connection should be released. If it does not happen then a waorkaround would be a manual
convertBodyTo as the converter closes the stream
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>                 Key: CAMEL-5138
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 2.8.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Christian Schneider
>             Fix For: 2.8.6, 2.9.3, 2.10.0
>         Attachments: CAMEL-5138-1.patch
> Even with streamCache set to false (which is the default situation), the HTTP (and HTTP4)
component (in producer mode) always create a CachedOutputStream.
> It should use a CachedOutputStream only if streamCache is true to the context.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message