There is currently no duplex option but it is on the list of things in the
future. Originally there was only upstream connections but I recently added
downstream configuration but it still requires creating a connection in
each direction.
The main issue is there is no current support for duplex connections in
Artemis to make it easy to implement (ServerLocator, etc create a new
connection and can't use existing). So it will take a little work to get
there but ultimately having real duplex connection is nice so the remote
broker doesn't have to know how to create a new connection.
On Wed, Feb 26, 2020 at 5:00 PM satees kumar kapu
wrote:
> We are trying to implement a hub and spoke topology using the Federation
> feature by configuring both upstream and downstream connections. In our
> case, we wanted to configure everything that is needed for the federation
> on
> the broker which is acting as spoke. This is mainly done this way as our
> main requirement was hub should not be aware of any spoke as spokes can be
> behind the firewall and are added or removed dynamically.
>
> In order to achieve this, In the downstream configuration, we set a
> share-connection flag that is supposed to use the same upstream connection
> to use for downstream communication. However, it seems we also required to
> configure the upstream-connector-ref which will be used by the hub to
> create
> a new connection to communicate. This is making Hub to aware of spoke which
> is violating our intend. Ideally, we want to avoid spoke's hostname the
> connector that is given in the upstream-connector-ref configuration.
>
> Is there any way to make the same connection Bi-directional/Duplex?
>
> In addition to that as spokes can be behind the firewall where only
> HTTP
> connections are allowed, can federation done via HTTP?
>
>
> Broker.xml on Hub
>
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:xi="http://www.w3.org/2001/XInclude;
>xsi:schemaLocation="urn:activemq
> /schema/artemis-configuration.xsd">
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="urn:activemq:core ">
> 0.0.0.0
>…
>
> name="netty-connector">tcp://0.0.0.0:61618
>
>
> name="netty-acceptor">tcp://0.0.0.0:61618
>
>
>
>
>name="exampleSubscription"/>
>
>
>
>
>
>
>
> Broker.xml on Spoke.
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:xi="http://www.w3.org/2001/XInclude;
>xsi:schemaLocation="urn:activemq
> /schema/artemis-configuration.xsd">
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="urn:activemq:core ">
> 0.0.0.0
>…
>
> name="netty-connector">tcp://spokeHostName:61618
>name="us-central-1-connector">tcp://hubHostName:61618
>
>
> name="netty-acceptor">tcp://0.0.0.0:61618
>
>
>
>
>
> 1000
>
> true
>
>
> us-central-1-connector
>
>
>
>
>
> 1000
>
> true
>
>
> us-central-1-connector
>
>
>
> netty-connector
>
>
>ref="address-federation" />
>
>
>address-match="exampleTopic" />
>
>
>
>
>
>
>name="exampleSubscription"/>
>
>
>
>
>
>
> Thanks in advance.
>
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
