[
https://issues.apache.org/jira/browse/CAMEL-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-7421:
-------------------------------
Fix Version/s: (was: Future)
2.15.0
> 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: 2.15.0
>
>
> 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)
