Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 14 Jul 2011 06:05:59 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1527968757.12463.1310623559973.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1836631061.10841.1310582939810.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CAMEL-4227) Seda component doesn't block on its
 blocking queue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen updated CAMEL-4227:
-------------------------------

         Priority: Minor  (was: Major)
    Fix Version/s: 2.9.0
       Issue Type: Improvement  (was: Bug)

You are welcome to contribute a patch for such a new option. You can read more about contributions here
http://camel.apache.org/contributing.html

> 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
>            Priority: Minor
>             Fix For: 2.9.0
>
>
> 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