[
https://issues.apache.org/jira/browse/CAMEL-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439098#comment-15439098
]
ASF GitHub Bot commented on CAMEL-10131:
----------------------------------------
GitHub user bogdanalbei opened a pull request:
https://github.com/apache/camel/pull/1144
CAMEL-10131 added exclusive queues support
Fix for https://issues.apache.org/jira/browse/CAMEL-10131
This is replacing #1138
Exclusive queues are used by only one connection and the queue will be
deleted when that connection closes. This is an important feature to have,
especially when using fanout exchanges, since the generated queues will not
autodelete when the client disconnects, leaving queues with no consumers
behind, which require manual/scripted intervention.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bogdanalbei/camel
CAMEL-10131-add-exclusive-queues-support-master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1144.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1144
----
commit 80d21843894c30fff68f48dab9e1c28d6b0ca544
Author: Bogdan Albei <[email protected]>
Date: 2016-08-26T14:06:19Z
CAMEL-10131 added exclusive queues support
----
> Add exclusive queues support to RabbitMQ component
> --------------------------------------------------
>
> Key: CAMEL-10131
> URL: https://issues.apache.org/jira/browse/CAMEL-10131
> Project: Camel
> Issue Type: Improvement
> Components: camel-rabbitmq
> Reporter: Bogdan Albei
> Assignee: Andrea Cosentino
> Priority: Minor
>
> Exclusive queues are used by only one connection and the queue will be
> deleted when that connection closes. At the moment the rabbitmq component
> does not support exclusive queues. I believe that it is an important feature
> to have, especially when using fanout exchanges, since the generated queues
> will not autodelete when the client disconnects, leaving queues with no
> consumers behind, which require manual/scripted intervention.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
