activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From exabrial <exabr...@gmail.com>
Subject Why does having a staticallyIncludedDestination create a consumer?
Date Wed, 11 May 2016 15:07:45 GMT
I'm creating a hub-spoke network of brokers. I'd like the edge brokers to
forward their messages to the hub so I don't have a ton of small backing
stores of messages hanging around.

So on the "spoke" broker, I have this network connector:

      <networkConnectors>
         <networkConnector
            name="tomee1_outbound_nc"
            duplex="true"
            networkTTL="2"
            uri="static:(tcp://localhost:61616)">
            <staticallyIncludedDestinations>
               <queue name=">" />
            </staticallyIncludedDestinations>
         </networkConnector>
      </networkConnectors>

When I connect it to the hub and log into the hub's admin console, it shows
a consumer has also been created. If I attach another spoke to the hub, the
message from the first spoke will get forwarded to the new spoke even though
no consumers have registered demand, and even odder yet, the hub shows that
two consumers now exist on the network.


I'm guessing that I'm misunderstanding how staticallyIncludedDestinations
works. Is there a way to forward the messages to the hub when it's
available, but store them locally if it's not?



--
View this message in context: http://activemq.2283324.n4.nabble.com/Why-does-having-a-staticallyIncludedDestination-create-a-consumer-tp4711832.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message