You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2019/03/20 14:45:51 UTC

[GitHub] [activemq-artemis] codybum commented on issue #2573: ARTEMIS-2265 Support Federated Queues and Addresses

codybum commented on issue #2573: ARTEMIS-2265 Support Federated Queues and Addresses
URL: https://github.com/apache/activemq-artemis/pull/2573#issuecomment-474863280
 
 
   Our transition to Artemis was on hold until federation came along, so this is a very exciting development.  We are making heavy use of 5.x network connectors and I hope this development can help us move forward. 
   
   A few questions:
   1.) Can federation (queue or topic) currently be used like a 5.x network connector, where we can dynamically (after broker has started) specific a remote participant via static address?  
   2.) Can the described connection be used bidirectionally?
   
   For instance, say you have two independent brokers, broker A and broker B, with public unicast ip address.  Broker A and B are not configured on startup to be aware of each other and neither have access to a multicast network.  Broker A is behind a firewall and can initiate IP connections to Broker B, but Broker B can't initiate connections to Broker A.
   
   Using a 5.x NetworkConnector a bidirectional connection can be made from Broker A to Broker B bridging the queues and topics on both brokers.  Is this or will this be possible using the existing federation implementation?
      
      

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services