[
https://issues.apache.org/activemq/browse/CAMEL-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashwin Karpe updated CAMEL-2526:
--------------------------------
Attachment: seda-maxconcurrentconsumers.patch
Hi Claus,
Please find attached a patch for this issue. I have tested it and it works fine.
BTW, I also added a flag, just in case there was someone out there who wanted
to explicitly bypass this setting. I have set the max concurrent consumers to
500 and added an info log message on the component to record the change in case
there is a component that runs into this ceiling.
I will commit it to the trunk since it is a rather trivial fix.
Cheers,
Ashwin...
> SedaConsumer - Add check to limit the concurrentConsumer to < 1000 to prevent
> mistypes
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-2526
> URL: https://issues.apache.org/activemq/browse/CAMEL-2526
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0.0, 2.1.0, 2.2.0
> Reporter: Claus Ibsen
> Assignee: Ashwin Karpe
> Priority: Trivial
> Fix For: 2.3.0
>
> Attachments: seda-maxconcurrentconsumers.patch
>
>
> If you enter concurrentConsumers=99999999 then Camel creates a lot of threads
> for concurrent consumers on the SEDA queue.
> We should validate the size is a reasonable value, at least < 1000. Maybe
> limit to < 500
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
