[
https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015001#comment-17015001
]
Christopher L. Shannon commented on ARTEMIS-355:
------------------------------------------------
[~masc3d] and [~jbertram] - That's right that currently federation does not
support a duplex bridge over the same connection. I just added downstream
support so brokers can be federated in either direction but this still requires
more than one connection. Eventually I am hoping to add true support for
sharing a single connection for cases where there are firewall issues just like
in AMQ 5.x. It will take a little bit of work to make it happen (primarily
would need to be able to spin off new client consumers from an existing already
established connection which is different than currently how ServerLocator
works) but it should be doable.
> Duplex bridges
> --------------
>
> Key: ARTEMIS-355
> URL: https://issues.apache.org/jira/browse/ARTEMIS-355
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 1.2.0
> Reporter: Mike Hearn
> Priority: Major
> Fix For: unscheduled
>
>
> I can't find any way to make an embedded artemis A connect to an embedded
> artemis B such that B can send messages to A without connectivity at the TCP
> level, e.g. due to firewall traversal. It'd be convenient if there was no
> need for me to implement firewall punching myself. Apparently ActiveMQ can do
> this using some sort of "duplex" attribute, but it's not in Artemis.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
