You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/11/04 18:19:52 UTC

[jira] Resolved: (CAMEL-2134) MulticastProccessor should default to reasonable thread pool and queue size

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

Claus Ibsen resolved CAMEL-2134.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.2

1.x: 832801.

Applied patch. Thanks a lot David. Keep 'em coming.

> MulticastProccessor should default to reasonable thread pool and queue size
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-2134
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2134
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.6.1
>            Reporter: David Valeri
>            Assignee: Claus Ibsen
>             Fix For: 1.6.2
>
>         Attachments: patch.txt
>
>
> The queue and thread pool are only as large as the number of endpoints that the multicast sends to.  I have been working with multicasts recently and found that you can very quickly overwhelm the default executor configured for a MulticastProcessor if you have a high message volume and/or concurrent consumers.  With the default redelivery policy in place, the exchanges may get redelivered to the multicast endpoints an arbitrary number of times which could be considered counter intuitive for novice users.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.