You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Mike Hearn (JIRA)" <ji...@apache.org> on 2016/02/05 15:31:39 UTC
[jira] [Commented] (ARTEMIS-355) Duplex bridges
[ https://issues.apache.org/jira/browse/ARTEMIS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134254#comment-15134254 ]
Mike Hearn commented on ARTEMIS-355:
------------------------------------
Yes, my use case is to have separate servers some of which may be on different sides of a corporate firewall. Being able to connect out of the firewall and then exchange messages bidirectionally is something a raw socket can do - it's a shame that this feature is lost when using Artemis. I honestly had not even considered that it may work this way, and now I'm wondering what the best fix or workaround may be until this issue is implemented (if it ever is? seems to be low priority?)
> 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
>
> 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)