Advisory broker replay of destination advisories needs to distinguish temp destination from regular destination

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.