[ 
https://issues.apache.org/activemq/browse/CAMEL-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58646#action_58646
 ] 

Claus Ibsen commented on CAMEL-2526:
------------------------------------

Ashwin I think it should thrown an IllegalArgumentException if 
concurrentConsumers > max.

Logging at INFO level just get unnoticed. At least it should log at WARN level 
instead.
But I would prefer to IllegalArgumentException instead.

Then that option limitConcurrentConsumers can be used to bypass and then you 
can have 9999 if you really want.



> 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.

Reply via email to