You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "David Valeri (JIRA)" <ji...@apache.org> on 2009/11/04 17:11:52 UTC
[jira] Created: (CAMEL-2134) MulticastProccessor should default to
reasonable thread pool and queue size
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
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.
[jira] Issue Comment Edited: (CAMEL-2134) MulticastProccessor
should default to reasonable thread pool and queue size
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55162#action_55162 ]
David Valeri edited comment on CAMEL-2134 at 11/4/09 8:20 AM:
--------------------------------------------------------------
Attached patch which mimics default executor configuration that was adopted in Camel 2.0. The patch provides for safer defaults at the expense of the risk of unbounded queue growth.
Perhaps a nod to this risk and the configuration defaults in the 1.6.x and 2.x documentation is also warranted.
was (Author: davaleri):
Attached path which mimics default executor configuration that was adopted in Camel 2.0. The patch provides for safer defaults at the expense of the risk of unbounded queue growth.
Perhaps a nod to this risk and the configuration defaults in the 1.6.x and 2.x documentation is also warranted.
> 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
> 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.
[jira] Updated: (CAMEL-2134) MulticastProccessor should default to
reasonable thread pool and queue size
Posted by "David Valeri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Valeri updated CAMEL-2134:
--------------------------------
Attachment: patch.txt
Attached path which mimics default executor configuration that was adopted in Camel 2.0. The patch provides for safer defaults at the expense of the risk of unbounded queue growth.
Perhaps a nod to this risk and the configuration defaults in the 1.6.x and 2.x documentation is also warranted.
> 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
> 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.
[jira] Assigned: (CAMEL-2134) MulticastProccessor should default to
reasonable thread pool and queue size
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-2134:
----------------------------------
Assignee: Claus Ibsen
> 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
> 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.
[jira] Resolved: (CAMEL-2134) MulticastProccessor should default to
reasonable thread pool and queue size
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.