You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jean-Baptiste Onofré (Created JIRA)" <ji...@apache.org> on 2012/04/03 15:40:23 UTC

[jira] [Created] (CAMEL-5138) HTTP component always use a CachedOutputStream

HTTP component always use a CachedOutputStream
----------------------------------------------

                 Key: CAMEL-5138
                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
             Project: Camel
          Issue Type: Bug
          Components: camel-http
    Affects Versions: 2.8.2
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré
             Fix For: 2.8.5, 2.10.0, 2.9.2


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Resolved] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-5138.
--------------------------------

    Resolution: Duplicate

Duplicate of CAMEL-4098
                
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 2.1.0, 2.8.2, 2.9.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Christian Schneider
>             Fix For: 2.8.6, 2.9.3, 2.11
>
>         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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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: https://issues.apache.org/jira/browse/CAMEL-5138
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5138:
-------------------------------

    Affects Version/s: 2.1.0
                       2.9.2
        Fix Version/s:     (was: 2.10.0)
                       2.11
    
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 2.1.0, 2.8.2, 2.9.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Christian Schneider
>             Fix For: 2.8.6, 2.9.3, 2.11
>
>         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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13247100#comment-13247100 ] 

Claus Ibsen commented on CAMEL-5138:
------------------------------------

This is a duplicate of https://issues.apache.org/jira/browse/CAMEL-4098
                
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 2.8.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.8.5, 2.10.0, 2.9.2
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Assigned] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider reassigned CAMEL-5138:
------------------------------------------

    Assignee: Christian Schneider  (was: Jean-Baptiste Onofré)
    
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             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
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262297#comment-13262297 ] 

Willem Jiang commented on CAMEL-5138:
-------------------------------------

@Christian
Please check out my comment in the CAMEL-4098. We still need to cache the input stream by default.
                
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             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
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5138:
-------------------------------

    Fix Version/s:     (was: 2.9.2)
                   2.9.3
    
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 2.8.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.8.5, 2.9.3, 2.10.0
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Willem Jiang (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254324#comment-13254324 ] 

Willem Jiang commented on CAMEL-5138:
-------------------------------------

HttpClient will close the InputStream automatically, when the connection is closed.
So we need to cache the InputStream in the HttpProducer before close the connection.
                
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 2.8.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.8.5, 2.9.3, 2.10.0
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (CAMEL-5138) HTTP component always use a CachedOutputStream

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea updated CAMEL-5138:
-----------------------------------

    Fix Version/s:     (was: 2.8.5)
                   2.8.6
    
> HTTP component always use a CachedOutputStream
> ----------------------------------------------
>
>                 Key: CAMEL-5138
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5138
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>    Affects Versions: 2.8.2
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.8.6, 2.9.3, 2.10.0
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira