[
https://issues.apache.org/jira/browse/ARTEMIS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222815#comment-17222815
]
Gary Tully commented on ARTEMIS-2964:
-------------------------------------
Advisories addresses ("ActiveMQ.Advisory.#") need permissions in the normal way.
Because openwire clients by default subscribe to temp destination advisories
(as a dubious optimisation), it may be necessary to disable this use of
advisories at the connection factory if the permissions are absent and there
are no other users of advisories.
This is achieved on the client using:
openwireConnectionFactory.setWatchTopicAdvisories(false) or via the broker
url parameter jms.watchTopicAdvisories=false
> Openwire ActiveMQ.Advisory.Connection does not fire
> ----------------------------------------------------
>
> Key: ARTEMIS-2964
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2964
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> it is not possible to consume the new connection advisory with Artemis.
> (topic Activemq.Advisory.Connection). The advisory fire fails b/c the
> internal session is used in error to fire advisories and that has not yet
> been created.
> The advisories should be routed directly in the same manner as management
> notifications.
> Note: to consume advisories, the appropriate permissions to create and
> receive must be present.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
