[ https://issues.apache.org/activemq/browse/AMQ-979?page=all ]
Rob Davies updated AMQ-979:
---------------------------
Description:
Network connections are generally one way - with messages only flowing out from
the broker that made the network connection.
In order to support WAN hub/spoke - where the central broker is behind a
firewall, and can only receive inbound connections, it is necessary to enable
optional b-idirectional network connections.
This issue was raised on the activemq-dev list:
http://www.nabble.com/Having-some-trouble-making-a-simple-network...-tf2449661.html
was:
Network connections are generally one way - with messages only flowing out from
the broker that made the network connection.
In order to support WAN hub/spoke - where the central broker is behind a
firewall, and can only receive inbound connections, it is necessary to enable
optional b-idirectional network connections.
> Allow NetworkConnections to bi-directional
> ------------------------------------------
>
> Key: AMQ-979
> URL: https://issues.apache.org/activemq/browse/AMQ-979
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Reporter: Rob Davies
> Assigned To: Rob Davies
> Fix For: 4.1
>
>
> Network connections are generally one way - with messages only flowing out
> from the broker that made the network connection.
> In order to support WAN hub/spoke - where the central broker is behind a
> firewall, and can only receive inbound connections, it is necessary to enable
> optional b-idirectional network connections.
> This issue was raised on the activemq-dev list:
> http://www.nabble.com/Having-some-trouble-making-a-simple-network...-tf2449661.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
