[
https://issues.apache.org/jira/browse/CAMEL-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4227.
--------------------------------
Resolution: Fixed
Thanks for the patch.
I have marked CollectionProducer as @deprecated.
I updated wiki page with the new option as well.
> Seda component doesn't block on its blocking queue
> --------------------------------------------------
>
> Key: CAMEL-4227
> URL: https://issues.apache.org/jira/browse/CAMEL-4227
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.7.2
> Reporter: Michael Allman
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: seda-blockWhenFull-patch.zip
>
>
> While one can put an upper bound on the size of the blocking queue that the
> seda component uses to queue messages, the seda component throws an exception
> when it reaches that limit instead of blocking. My understanding of a
> blocking queue is that the upper bound lets you put an upper bound on the
> queue and block when it becomes full. The fact that the seda component throws
> an exception makes the upper bound useless in practice, unless there is
> supposed to be some kind of easy workaround. We have not found one, and it
> looks like we will be rolling our own async component to compensate. :(
> The basic issue is that SedaProducer calls BlockingQueue.add() instead of
> BlockingQueue.put().
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
