camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7421) camel-rabbitmq - Channel is not fully thread safe
Date Wed, 03 Dec 2014 08:01:12 GMT

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

Claus Ibsen commented on CAMEL-7421:
------------------------------------

I think its better to use commons-pool as the pooling implementation, instead of writing your
own. 
We do this with camel-netty etc.

> camel-rabbitmq - Channel is not fully thread safe
> -------------------------------------------------
>
>                 Key: CAMEL-7421
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7421
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-rabbitmq
>    Affects Versions: 2.12.3
>            Reporter: GĂ©rald Quintana
>             Fix For: Future
>
>
> Channels are not fully thread-safe (see below), as a result the RabbitMQProducer shouldn't
use a single Channel. In short, Channels should be pooled, and each thread given a Channel
from the pool.
> http://www.rabbitmq.com/api-guide.html#channel-threads 
> {quote}applications should prefer using a Channel per thread instead of sharing the same
Channel across multiple threads.{quote}
> http://www.rabbitmq.com/javadoc/com/rabbitmq/client/Channel.html 
> {quote}An important caveat to this is that confirms are not handled properly when a Channel
is shared between multiple threads. In that scenario, it is therefore important to ensure
that the Channel instance is not accessed concurrently by multiple threads.{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message