The bridge broker name is used as an identity for that bridge's durable consumers. With a durable consumer, a bridge subscription needs to remain through a durable connect/close. This is achieved by using a well known name for the durable subscription in the bridge. This name is based on the bridge's broker name. This ensures that the bridge subscription remains through a durable subscription close/reopen and that the reopened subscription can reconnect with the original bridge's subscription.
For full details see createDemandSubscription @ http://activemq.apache.org/maven/activemq-core/apidocs/src-html/org/apache/activemq/network/DurableConduitBridge.html#line.79 2009/3/2 Bastian Preindl <bastian.prei...@joinvision.com>: > > Hi, > > apparently my mistake was to copy and paste the configuration from one > broker to the others and not change the broker's name ('localhost'). But I > wonder why this doesn't lead to problems from the beginning but as recently > as I add the second durable subscriber to a broker having the same name that > the first subscriber's broker. When establishing the bridges everything > works fine. > > I'd really appreciate any clarification on this because now it works but I > don't really know why?! > > Thanks a lot > > Bastian > -- > View this message in context: > http://www.nabble.com/Network-of-3-brokers%2C-durable-consumer-problem-tp22262226p22286296.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com
