[
https://issues.apache.org/jira/browse/AMQ-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160827#comment-13160827
]
Gary Tully commented on AMQ-3615:
---------------------------------
note: came across this looking at the org.apache.activemq.bugs.AMQ3454Test case
a little more carefully to examine the contention on destinationMap. There
should be no temp advisories in that test.
> Advisory broker replay of destination advisories needs to distinguish temp
> destination from regular destination
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3615
> URL: https://issues.apache.org/jira/browse/AMQ-3615
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.1
> Reporter: Gary Tully
> Labels: advisory, temp
>
> By default an activemq connection registers an advisory consumer for temp
> destinations. This is configurable via: {{jms.watchTopicAdvisories}}. This
> allow the client to respond to a request to a deleted temp destination
> without a round trip to the broker and avoid a possible auto creation.
> At the moment, that advisory consumer gets notified of *all* destinations,
> not just temp destinations. So if there are large amounts of destinations,
> there is an unnecessary flood of advisories on the initial subscribe.
> The workaround, for clients who don't use temps is to disable this advisory
> monitor, using {{jms.watchTopicAdvisories=false}} on the connection factory
> broker url or setting the corresponding property on the connection factory or
> connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
