[
https://issues.apache.org/jira/browse/QPID-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415860#comment-16415860
]
Artyom Safronov edited comment on QPID-7541 at 3/27/18 4:18 PM:
----------------------------------------------------------------
I found other odd behavior.
Next steps were done:
* 3 queues were created
* after while they were deleted
* my app found that because REST API returned no queues
* my app sent close requests (one by one) to the broker *but received all
responses after the first request* (see [^batch_responses.log])
was (Author: artyom82):
I found other odd behavior.
Next steps were done:
* 3 queues were created
* after while they were deleted
* my app found that because REST API returned no queues
* my app sent close requests (one by one) to the broker *but received all
responses after the first request* (see the log)
> [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
> Fix For: qpid-java-broker-7.0.3
>
> Attachments: batch_responses.log, proton-j_client.log
>
>
> Currently when a Queue is deleted the associated Consumers are not closed.
> This is essentially a resource leak.
> Note: In 6.1.x, for the AMQP 1.0 protocol, deleting a queue did detach the
> sending links (without error). Receiving links were not detached. This
> code (org.apache.qpid.server.protocol.v1_0.ConsumerTarget_1_0#queueDeleted)
> was removed in 7.0.x and this JIRA raised.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
