Description
Typically network require advisory message to allow peer broker to know about dynamic destination and consumer creation. However the advisory overhead can be significant as the numbers of peer brokers in a network increase to double digits.
A statically configured network can exist without advisories but using request reply with temporary currently destinations fails: a) because there is no way to configure them as statically included as their generated name is dynamically created from a connectionId and does not contain a wild card separator '.'. b) it is not possible to auto create a temp destination by a replying message producer (AMQ-2571)
Some discussion at: http://mail-archives.apache.org/mod_mbox/activemq-users/201103.mbox/%3CAANLkTi=N3LaQ4AWP8hK48OYAgWpSVodvjw4AN57j3+vz@mail.gmail.com%3E