[
https://issues.apache.org/jira/browse/CAMEL-16619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-16619:
--------------------------------
Summary: camel-rabbitmq - Producer destroys rabbit channels when returns it
back to the pool (was: Producer destroys rabbit channels when returns it back
to the pool)
> camel-rabbitmq - Producer destroys rabbit channels when returns it back to
> the pool
> -----------------------------------------------------------------------------------
>
> Key: CAMEL-16619
> URL: https://issues.apache.org/jira/browse/CAMEL-16619
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
> Affects Versions: 3.7.4
> Reporter: Anton Ovcharenko
> Priority: Major
> Fix For: 3.7.5, 3.11.0
>
>
> It was noticed that
> _{{org.apache.camel.component.rabbitmq.RabbitMQProducer}}_ uses
> _{{org.apache.commons.pool.impl.GenericObjectPool}}_ for managing channels
> pool.
> This implementation leads to permanent recreation of channels if we try to
> manage high rate of messages .
> When the producer was configured with _{{channelPoolMaxSize}}_ value more
> than 8 (this is equals to
> _{{org.apache.commons.pool.impl.GenericObjectPool#DEFAULT_MAX_IDLE}}_) this
> pool destroys channel on returning it to the pool
> ([GenericObjectPool|https://github.com/mariusae/commons-pool/blob/9ba5ede723916e76626bc2b3cd38e63bd1fa58d4/src/java/org/apache/commons/pool/impl/GenericObjectPool.java#L1406]).
>
> The solution is to specify _{{maxIdle}}_ during pool creation
> ({{_org.apache.camel.component.rabbitmq.RabbitMQProducer#openConnectionAndChannelPool_}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
