[
https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16399427#comment-16399427
]
Keith Wall commented on QPID-7541:
----------------------------------
Yes - this is certainly a gap and something I would like to fix soon. For AMQP
1.0 connections, I think the Broker ought to be
[detaching|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-detach]
the link with an appropriate error. The older protocols, AMQP 0-10 and AMQP
0-8..91 didn't really make provision for this. They have a {{message.cancel}}
and {{basic.cancel}} (respectively) but these where defined as sent from a
client to server and not the other way around. For these protocols all that
can be done is to close the session/channel or the close the entire connection.
Artyom, which client library are you using with the Broker?
> [Java Broker] Close Consumers when a Queue is deleted
> -----------------------------------------------------
>
> Key: QPID-7541
> URL: https://issues.apache.org/jira/browse/QPID-7541
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Reporter: Lorenz Quack
> Priority: Major
>
> Currently when a Queue is deleted the associated Consumers are not closed.
> This is essentially a resource leak.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
