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

Gérald Quintana updated CAMEL-7384:
-----------------------------------

    Description: 
Several settings of the {{com.rabbitmq.client.ConnectionFactory}} are not 
exposed in RabbitMQEndpoint, namely:
- automaticRecoveryEnabled
- networkRecoveryInterval
- topologyRecoveryEnabled
- connectionTimeout
- requestedHeartbeat
- clientProperties
- requestedChannelMax
- requestedFrameMax
- sslProtocol

It would be great if we could plug any ConnectionFactory implementation in the 
endpoint (caching connection factory for instance)

  was:
Several settings of the {{com.rabbitmq.client.ConnectionFactory}} are not 
exposed in RabbitMQEndpoint, namely:
- automaticRecoveryEnabled
- networkRecoveryInterval
- topologyRecoveryEnabled
- connectionTimeout
- requestedHeartbeat
- clientProperties
- exceptionHandler
- requestedChannelMax
- requestedFrameMax
- sslProtocol

It would be great if we could plug any ConnectionFactory implementation in the 
endpoint, in particular the 
{{org.springframework.amqp.rabbit.connection.CachingConnectionFactory}} from 
Spring Rabbit project


> camel-rabbitmq: Allow connection factory tuning
> -----------------------------------------------
>
>                 Key: CAMEL-7384
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7384
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-rabbitmq
>    Affects Versions: 2.13.0
>            Reporter: Gérald Quintana
>
> Several settings of the {{com.rabbitmq.client.ConnectionFactory}} are not 
> exposed in RabbitMQEndpoint, namely:
> - automaticRecoveryEnabled
> - networkRecoveryInterval
> - topologyRecoveryEnabled
> - connectionTimeout
> - requestedHeartbeat
> - clientProperties
> - requestedChannelMax
> - requestedFrameMax
> - sslProtocol
> It would be great if we could plug any ConnectionFactory implementation in 
> the endpoint (caching connection factory for instance)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to