camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-7087) StreamCache does not reset at the end of the pipeline
Date Fri, 20 Dec 2013 17:28:36 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-7087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-7087.
--------------------------------

    Resolution: Fixed

Thanks for reporting and the patch.

> StreamCache does not reset at the end of the pipeline
> -----------------------------------------------------
>
>                 Key: CAMEL-7087
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7087
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.12.2
>            Reporter: Stephan Siano
>            Assignee: Claus Ibsen
>             Fix For: 2.12.3, 2.13.0
>
>         Attachments: 0001-CAMEL-7087-StreamCache-does-not-reset-at-the-end-of-.patch
>
>
> The StreamCache does not reset at the end of the pipeline.
> The following routes will not work as expected:
>    from("direct:c").noStreamCaching().to("direct:d").to("mock:c");
>    from("direct:d").streamCaching().process(new TestProcessor());
> (the test processor is a processor that reads the InputMessage)
> If another processor is added after the TestProcessor that does nothing, the routes will
work as expected.
> This case is a bit synthetic, but in real life a route that starts with a InOut CXF endpoint,
has an endpoint that generates a Stream and then writes the message content to an in only
endpoint (file, FTP, log, etc.) will also fail, even if stream caching is enabled.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message