Return-Path: <dev-return-56694-archive-asf-public=cust-asf.ponee.io@activemq.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 9BB5C200BCA
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon, 21 Nov 2016 15:19:30 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 9A663160AF9; Mon, 21 Nov 2016 14:19:30 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id E1B12160AEC
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 21 Nov 2016 15:19:29 +0100 (CET)
Received: (qmail 76243 invoked by uid 500); 21 Nov 2016 14:19:29 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Delivered-To: moderator for dev@activemq.apache.org
Received: (qmail 87789 invoked by uid 99); 21 Nov 2016 05:03:41 -0000
X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 3.801
X-Spam-Level: ***
X-Spam-Status: No, score=3.801 tagged_above=-999 required=6.31
	tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25,
	NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001,
	SPF_SOFTFAIL=0.972, URI_HEX=1.313, URI_TRY_3LD=0.065]
	autolearn=disabled
Date: Sun, 20 Nov 2016 20:51:21 -0800 (PST)
From: vamit100 <vamit100@gmail.com>
To: dev@activemq.apache.org
Message-ID: <1479703880681-4719319.post@n4.nabble.com>
In-Reply-To: <1385013685950-4674710.post@n4.nabble.com>
References: <1310373613913-3658967.post@n4.nabble.com> <CAGeh-pHL8CdvQEY3bLsQZL=nhgQwSKsSSHU6fH6+bt2v1nsjxg@mail.gmail.com> <1385013685950-4674710.post@n4.nabble.com>
Subject: Re: Discovery without multicast (like on EC2)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Mon, 21 Nov 2016 14:19:30 -0000

Hi,

I tried above mentioned broker configuration with activemq 5.14.1 . But it
is not working. I have three brokers and HAproxy as a load balancer.

Suppose broker1IP, broker2IP, broker3IP are ip addresses of brokers and
haproxyIP is ip address HAProxy VM. 61616 is openwire port for activemq.
(Note : All brokers are on different machines. Also there is separate
machine for HAProxy)

In addition to above mentioned configuration, here is customized
configuration on my side.

*1. HAProxy Configuration file*

defaults
    mode tcp
	
frontend MessagingBroker
    bind *:61616
    default_backend nodes
    
backend nodes
    balance roundrobin
    server web01 broker1IP:61616 check
    server web02 broker2IP:61616 check
    server web03 broker3IP:61616 check

listen stats *:8080
    mode http
    stats enable
    stats uri /
    stats hide-version
    stats auth admin:admin

frontend discovery
    mode http
    bind *:61618
    default_backend discovery_nodes
    
backend discovery_nodes
    mode http
    balance roundrobin
    server web01 broker1IP:61618 check
    server web02 broker2IP:61618 check
    server web03 broker3IP:61618 check
*
2. Addition of network connector in activemq.xml file
*

<networkConnectors> 
              <networkConnector name="default"
uri="http://haproxyIP:61618/activemq/DiscoveryRegistryServlet?group=test"/> 
               </networkConnectors>

*3. Addition of new transport connector:* Addition of below transport
connector to activemq.xml file. This is in addition to Openwire transport
connector. I just added below new transport connector for http discovery.

 <transportConnectors> 
                    <transportConnector name="http"
uri="tcp://0.0.0.0:61618"
discoveryUri="http://haproxyIP:61618/activemq/test"/> 
                </transportConnectors> 


*4. I have not added any jars as all optional jars are already present in
activemq 5.14.1 . *


       Using this configuration, I am able to successfully connect to
different different brokers using uri failover:(tcp://haproxyIP:61616) from
client side. This means that HAProxy is working fine. But, these three
brokers are not getting inter-connected to each other using http discovery.
I want to create network of brokers.

Please let me know how can I successfully create network of brokers using
http discovery.

Thanks for Help. 



--
View this message in context: http://activemq.2283324.n4.nabble.com/Discovery-without-multicast-like-on-EC2-tp3658967p4719319.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.