You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/30 14:42:21 UTC
[jira] [Commented] (ARTEMIS-762) AMQP Clients are not updated after
management operations
[ https://issues.apache.org/jira/browse/ARTEMIS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15536167#comment-15536167 ]
ASF GitHub Bot commented on ARTEMIS-762:
----------------------------------------
GitHub user mtaylor opened a pull request:
https://github.com/apache/activemq-artemis/pull/814
ARTEMIS-762 Reflect management changes in AMQP protocol
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-762
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/814.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 #814
----
commit 64ddc776fcd784fe31b11a6bb1b07aab95086b53
Author: Ulf Lilleengen <ul...@redhat.com>
Date: 2016-09-30T14:35:59Z
ARTEMIS-762 Reflect management changes in AMQP protocol
----
> AMQP Clients are not updated after management operations
> --------------------------------------------------------
>
> Key: ARTEMIS-762
> URL: https://issues.apache.org/jira/browse/ARTEMIS-762
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Martyn Taylor
>
> Management operations may remove connections, queues, stop consumers etc... However, with AMQP clients connected, these operations should result in the client being updated via the relevant AMQP frames. This is currently not implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)