[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Re: Reply message not forwarded across temporary bridged destination
From:       Tim Bain <tbain () alumni ! duke ! edu>
Date:       2015-07-31 2:30:36
Message-ID: CAPVVMa8Eu2_sHeKCqtd=H6aGrfc54DQCOpmosQhzJrtqkTcqcg () mail ! gmail ! com
[Download RAW message or body]


Thanks for clarifying your use-case.

In response to your original questions:

   1. getPhysicalName() returns a String, which allows wildcards (*, >, and
   I think <, though that might be a 5.11 feature, I don't remember).
   2. The staticallyIncludedDestinations attribute controls which
   destinations the current broker is allowed to forward messages for to the
   broker at the other end of the networkConnector.  This means that you'll
   want two non-duplex networkConnectors per hub/spoke pair, with each one
   including the destinations that should go to the other broker.
   3. I thought I'd seen such a thing in the past, but couldn't find it in
   response to a previous question and I believe that person got things
   working successfully without it.  So you may be able to successfully ignore
   it; at least give it a shot without and see how it goes.

BTW, http://activemq.apache.org/networks-of-brokers.html has some examples
of the staticallyIncludedDestinations attribute in a XML file, if you're
still not quite sure what it should look like.

Hope this gets you to a working configuration; let us know what's not
working if it doesn't.

Tim

On Thu, Jul 30, 2015 at 3:26 PM, Gregg Saffell <gsaffell@ilstechnology.com>
wrote:

> Yes, I want to use statically defined queues exclusively.  The hub is in NY
> and the spokes are all around the world, network outages are not rare and
> one of our uses for AMQ is propagating usage data to a central location. As
> a result, we have a long expiration on the messages (2 weeks) and want them
> to collect on the spokes even when the hub is not connected.
> 
> We have queues that exist just at the hub and one spoke (for messages going
> to the spoke) and queues that exist at all sites (for messages going to the
> hub). I'm using <staticallyIncludedDestinations> to ensure only the queues
> relevant to a particular spoke are created there.
> 
> In my app, there should be no dynamically created queues. As a precaution,
> I
> would like to prevent any such queues that do get created (say, via a
> programming error or a bug in AMQ) from being replicated to any spokes.
> 
> 
> 
> 
> 
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Reply-message-not-forwarded-across-temporary-bridged-destination-tp4688578p4700169.html
>  Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> 



[prev in list] [next in list] [prev in thread] [next in thread]