Mule
  1. Mule
  2. MULE-6104

request-reply router, collection-splitter and collection-aggregator triplet bug

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Won't Fix or Usage Issue
    • Affects Version/s: 3.2.1
    • Fix Version/s: None
    • Component/s: Core: Request-Reply
    • Labels:
      None
    • Environment:

      CE

    • User impact:
      Very High
    • Configuration:
      Show
      http://pastebin.com/KZK5jzZ5 I believe this to be related to http://www.mulesoft.org/jira/browse/MULE-5860 .
    • Log Output:
      <vm:inbound-endpoint path="work2reply" exchange-pattern="one-way"/> is never called after aggregation (<collection-aggregator/>) unless followed by a <combine-collections-transformer/>
    • Migration Impact:
      Makes synchronous request - asynchronous split/work/aggregate -> synchronous response message processing impossible through implicit documentation features.
    • Similar Issues:
      None

      Description

      When using a request-reply router with asynchronous outbound and inbound endpoints, the inbound endpoint is never called with the asychronous processing invokes a collection-splitter -> collection aggregator pair.

        Activity

        Hide
        Matias Baldini added a comment -

        Mule issues cleanup.

        Show
        Matias Baldini added a comment - Mule issues cleanup.

          People

          • Assignee:
            Unassigned
            Reporter:
            Franco Gasperino
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development