Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 16 May 2016 09:43:49 -0400 (EDT)
From: Justin Bertram <jbertram@apache.com>
To: dev@activemq.apache.org
Message-ID: <103528439.3205320.1463406229914.JavaMail.zimbra@redhat.com>
In-Reply-To: <1463246436100-4711941.post@n4.nabble.com>
References: <1463246436100-4711941.post@n4.nabble.com>
Subject: Re: [Artemis]  Bug in ServerLocatorImpl.createSessionFactory()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: Bug in ServerLocatorImpl.createSessionFactory()
Thread-Index: rbEXENDEr+lMOSbRTwvZNmrNpgyvLw==
archived-at: Mon, 16 May 2016 13:44:03 -0000

Can you elaborate on why you would front the broker with a proxy?  I'm not familiar with this use-case.


Justin

----- Original Message -----
From: "abhijith" <topcoderabhijith@gmail.com>
To: dev@activemq.apache.org
Sent: Saturday, May 14, 2016 12:20:36 PM
Subject: [Artemis]  Bug in ServerLocatorImpl.createSessionFactory()

Hi,

I think there is a bug in ServerLocatorImpl.createSessionFactory() method. 
Issue is that if factory.connect(initialConnectAttempts,
failoverOnInitialConnection) is successful, it is always assumed that client
should be able to download Cluster Toplogy.

This might not be the case for any broker which is fronted with a proxy. 
Proxy always accepts connection regardless of broker behind is up or down. 
This method should try out all available initialConnectors to download
cluster topology before erroring out.

I raised this question in user forum and then looked into the code on
exactly what it is doing.  Please let me know if I am missing something
here.

Thanks
Abhi


--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Bug-in-ServerLocatorImpl-createSessionFactory-tp4711941.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.