Hi Tim ,
I am writing a simple java client to get the broker service instance of my
remote broker which is in dev environment. I have seen several examples
related to brokers service which they are starting up locally and using that
local instance ..But in my case the brokers are already up and r
I think he means the SASL EXTERNAL mechanism for authentication.
J.
On Sat, May 14, 2016 at 11:29 PM, John D. Ament
wrote:
> Vavricka,
>
> In this case, what do you mean by external? are you considering the
> difference between the in vm connection factory and an AMQP connection
> factory?
>
>
Vavricka,
In this case, what do you mean by external? are you considering the
difference between the in vm connection factory and an AMQP connection
factory?
John
On Fri, May 13, 2016 at 8:15 AM Vavricka wrote:
> Hi,
>
>I am trying to restrict SASL mechanisms. I could not find how to do i
It's expected that you won't fail back to node1 when both are up (though
you can configure it to do so, see the Priority Backup section of
http://activemq.apache.org/failover-transport-reference.html), but it's
definitely not expected that you would not fail over to node1 if it was the
only live br
Others might, but I don't understand what you're asking. Can you explain,
or maybe post the code you're trying to get working?
On May 13, 2016 9:45 AM, "akhil" wrote:
> I have a use case where i have to get the broker service instance for the
> remote broker or getting the remote broker instance
I have been moving some of my clients to use the failover url using below.
url=
"failover:(tcp://node1:61616?useInactivityMonitor=false,
tcp://node2:61616?useInactivityMonitor=false)?randomize=false;";
I bring down node1, client is able to read/write message by connecting to
node2.
