You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2021/03/03 17:52:00 UTC
[jira] [Commented] (AMQ-4815) Providing additional advisory options
on per-destination basis
[ https://issues.apache.org/jira/browse/AMQ-4815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294699#comment-17294699 ]
Matt Pavlovich commented on AMQ-4815:
-------------------------------------
This has been added in newer release of ActiveMQ see: [Destination Policies|https://activemq.apache.org/per-destination-policies]
> Providing additional advisory options on per-destination basis
> --------------------------------------------------------------
>
> Key: AMQ-4815
> URL: https://issues.apache.org/jira/browse/AMQ-4815
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Dmitry Salychev
> Priority: Minor
>
> I want to deal with advisory messages only for specified destinations and avoid all advisory messages from other to achieve as small as possible memory and connections overhead.
> This is can be done on a per-destination basis like that:
> {noformat}
> <broker advisorySupport="true" ...>
> ...
> <destinationPolicy>
> <policyMap>
> <policyEntries>
> <policyEntry topic="api.>" creatingAdvisory="true"/>
> ...
> {noformat}
> In the background, I want to use org.apache.activemq.advisory.DestinationSource(It is based on the advisory messages from ActiveMQ.Advisory.Topic, isn't it?) for many topics on many brokers with minimum overhead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)