You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/03/31 17:20:05 UTC

[jira] [Resolved] (AMQ-3253) Support Temporary Destinations in a network without advisories

     [ https://issues.apache.org/jira/browse/AMQ-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3253.
-----------------------------

    Resolution: Fixed

http://svn.apache.org/viewvc?rev=1087330&view=rev
Added support for configuring the prefix used by connections such that the identity of temp destinations can be controlled. Using a prefix like 'ID:marker.X' allows a wild card matching temp destination to be statically included in a network bridge.
The temp destination created for a reply is associated with the connection of the reply message producer.
There is an example of the xml and programatic configuration in http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/RequestReplyNoAdvisoryNetworkTest.java?view=markup&pathrev=1087330

> Support Temporary Destinations in a network without advisories
> --------------------------------------------------------------
>
>                 Key: AMQ-3253
>                 URL: https://issues.apache.org/jira/browse/AMQ-3253
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.6.0
>
>
> 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

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira