[
https://issues.apache.org/jira/browse/ARTEMIS-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258945#comment-16258945
]
ASF subversion and git services commented on ARTEMIS-1365:
----------------------------------------------------------
Commit 5fe88e1c667870a398d85e427d324542399f9dfe in activemq-artemis's branch
refs/heads/master from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=5fe88e1 ]
ARTEMIS-1365 Advisory consumers listed in Console
Openwire clients create consumers to advisory topics to receive
notifications. As a result there are internal queues created
on advisory topics. Those consumer shouldn't be exposed via
management APIs which are used by the Console
To fix that the broker doesn't register any queues from
advisory addresses.
Also refactors a code to remove Openwire specific contants
from AddressInfo class.
> Openwire producer is listed in hawtio console as consumer from
> ActiveMQ.Advisory queue
> ---------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1365
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1365
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.3.0
> Environment: latest upstream 2.3.0 with hawtio
> Reporter: Michal Toth
> Assignee: Howard Gao
> Priority: Critical
> Attachments: openwire.png
>
>
> Having one openwire jms client which is sending messages to queue is listed
> in new console as consumer from activemq.advisory multicast queue. There is
> no information about producing messages to any queue at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
