camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Franz Forsthofer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-7787) Multicast - Should defer UoW done until after the aggregate has been done
Date Fri, 19 Sep 2014 09:20:33 GMT

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

Franz Forsthofer updated CAMEL-7787:
------------------------------------
    Attachment: 0001-stream-caching-in-sub-routes-of-splitter-and-multi-c.patch

We found an additional case where a problem can occur: nesting of splitter/mulitcast where
the aggregation strategy returns a stream cache.
We fixed this also in the new uploaded patch.

> Multicast - Should defer UoW done until after the aggregate has been done
> -------------------------------------------------------------------------
>
>                 Key: CAMEL-7787
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7787
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, eip
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.15.0
>
>         Attachments: 0001-stream-caching-in-sub-routes-of-splitter-and-multi-c.patch
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Stream-Cache-spool-file-deletion-before-aggregation-in-Multicast-involving-huge-data-tp5756092.html
> In the multicast/splitter we should defer the UoW done to *after* the aggregate has been
called, as in the nabble example, the stream cache overflow to disk would have deleted the
file etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message