You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "masc (JIRA)" <ji...@apache.org> on 2016/12/29 16:17:58 UTC

[jira] [Comment Edited] (ARTEMIS-355) Duplex bridges

    [ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785610#comment-15785610 ] 

masc edited comment on ARTEMIS-355 at 12/29/16 4:17 PM:
--------------------------------------------------------

As I understand the documentation a single JMS bridge is closely tied to a single source/target destination pair. Just to make sure I understand you correctly. Are JMS bridges really a viable temporary solution if you need seamless duplex connectivity for all JMS destinations across all nodes of a broker network?



was (Author: masc3d):
As I understand the documentation JMS bridges are closely tied to a single source/target destination pair. Just to make sure I understand you correctly. Are JMS bridges really a viable temporary solution if you need seamless duplex connectivity for all JMS destinations across all nodes of a broker network?


> 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
>            Assignee: Martyn Taylor
>             Fix For: 2.0.0
>
>
> 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
(v6.3.4#6332)