Thank Gary.
by using the updateURIsSupported=false in the failover uri my problem is
solved.
Thanks a lot.
-
Thanks and Regards,
Rahul
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Not-able-to-configure-JDBC-Master-Slave-Clustering-in-ActiveMQ-5-4-2-tp3316794p3317
Try with updateURIsSupported=false on the failoveruri, that will stop
the auto update and ensure that the clients url list is static.
It looks like the duplex network may be causing an issue for the
dynamic update feature, I know there was some change on trunk related
to that in the past weeks.
Pos
Hi, as per your suggestion i have taken the trace level log for
failoverTransport Class.
First time it is successfully connected to one of the broker.
When i shutdown the connected borker, it is getting below urlLIst for making
connections
urlList connectionList:[tcp://DT21764:51616, tcp://DT217
enable trace level logging of the FailoverTransport class on your client so
see what is going on.
On 21 February 2011 04:05, rkparikh wrote:
>
> Hi,
>
> I am trying to configure the JDBC Master/Slave clustering with two
> brokers(says BrokerA and BrokerB) on local machines.
>
> I have follow the
Hi,
I am trying to configure the JDBC Master/Slave clustering with two
brokers(says BrokerA and BrokerB) on local machines.
I have follow the below steps to check
1. Start the brokerA.
- it gets the lock on DB table.
2. Start the brokerB
- it is trying to get the lock but not getti
