You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by David Laube <da...@stormpath.com> on 2014/01/28 23:41:38 UTC
Duplex networkConnector with SSL based failover transport on ActiveMQ 5.9.0.
Hi All,
We are attempting to use a duplex networkConnector on a cluster that needs to "talk" to another cluster within the same network. Ideally, we would like to encrypt the traffic between the two clusters, all while maintaining HA by use of the failover transport. We have attempted to accomplish this by defining the following config entry:
<networkConnector name="environment-amq-broker-public-1" duplex="true" uri="static:(failover://(ssl://BROKER_MASTER_IP_HERE:61617,ssl://BROKER_SLAVE_IP_HERE:61617)?randomize=false&timeout=15000)"
Is this functionality supported within ActiveMQ 5.9.0? Or does anyone spot any glaring issues with the config above?
Best regards,
-David Laube
Re: Duplex networkConnector with SSL based failover transport on
ActiveMQ 5.9.0.
Posted by dlaube <dl...@gmail.com>.
Looks like the move the masterslave instead of static + removing the failover
transport did the trick --thanks!
We ended up using the following;
<networkConnector name="staging-amq-broker-public-1" duplex="true"
uri="masterslave:(ssl://BROKER_MASTER_IP_HERE:61617,ssl://BROKER_SLAVE_IP_HERE:61617)?randomize=false&timeout=15000"
Thanks again,
-David Laube
--
View this message in context: http://activemq.2283324.n4.nabble.com/Duplex-networkConnector-with-SSL-based-failover-transport-on-ActiveMQ-5-9-0-tp4677041p4677209.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Duplex networkConnector with SSL based failover transport on
ActiveMQ 5.9.0.
Posted by Gary Tully <ga...@gmail.com>.
correction, masterSlave: in place of static:
On 30 January 2014 16:44, Gary Tully <ga...@gmail.com> wrote:
> use static:(masterSlave:....) - failover reconnection is not supported
> for networkconnectors, the networkconnector needs to die and get
> recreated by the 'static' discovery mechanism.
> see:
>
> MasterSlave Discovery section of
> http://activemq.apache.org/networks-of-brokers.html
>
> On 28 January 2014 22:41, David Laube <da...@stormpath.com> wrote:
>> Hi All,
>>
>> We are attempting to use a duplex networkConnector on a cluster that needs to "talk" to another cluster within the same network. Ideally, we would like to encrypt the traffic between the two clusters, all while maintaining HA by use of the failover transport. We have attempted to accomplish this by defining the following config entry:
>>
>> <networkConnector name="environment-amq-broker-public-1" duplex="true" uri="static:(failover://(ssl://BROKER_MASTER_IP_HERE:61617,ssl://BROKER_SLAVE_IP_HERE:61617)?randomize=false&timeout=15000)"
>>
>> Is this functionality supported within ActiveMQ 5.9.0? Or does anyone spot any glaring issues with the config above?
>>
>> Best regards,
>> -David Laube
>
>
>
> --
> http://redhat.com
> http://blog.garytully.com
--
http://redhat.com
http://blog.garytully.com
Re: Duplex networkConnector with SSL based failover transport on
ActiveMQ 5.9.0.
Posted by Gary Tully <ga...@gmail.com>.
use static:(masterSlave:....) - failover reconnection is not supported
for networkconnectors, the networkconnector needs to die and get
recreated by the 'static' discovery mechanism.
see:
MasterSlave Discovery section of
http://activemq.apache.org/networks-of-brokers.html
On 28 January 2014 22:41, David Laube <da...@stormpath.com> wrote:
> Hi All,
>
> We are attempting to use a duplex networkConnector on a cluster that needs to "talk" to another cluster within the same network. Ideally, we would like to encrypt the traffic between the two clusters, all while maintaining HA by use of the failover transport. We have attempted to accomplish this by defining the following config entry:
>
> <networkConnector name="environment-amq-broker-public-1" duplex="true" uri="static:(failover://(ssl://BROKER_MASTER_IP_HERE:61617,ssl://BROKER_SLAVE_IP_HERE:61617)?randomize=false&timeout=15000)"
>
> Is this functionality supported within ActiveMQ 5.9.0? Or does anyone spot any glaring issues with the config above?
>
> Best regards,
> -David Laube
--
http://redhat.com
http://blog.garytully.com