that deal with this, but the info above may give
> you
> key words that can help in your research.
>
>
> On 22 April 2010 10:13, TonyTobin wrote:
>
>>
>> Thanks Gary,
>>
>> That makes sence.
>>
>>
>> Are there any decent links on the di
he
> primary (because it got there first) and when/if it fails, it will deliver
> messages to the second consumer (the hot standby). So the broker chooses
> but
> only from among the current active consumers.
>
> On 22 April 2010 09:09, TonyTobin wrote:
>
>>
>> Than
the
> messages. If effectively allows consumers to stack waiting for the current
> consumer to die.
>
> On 21 April 2010 16:35, TonyTobin wrote:
>
>>
>> In the ActiveMQ doc http://activemq.apache.org/exclusive-consumer.html it
>> states
>>
>> The brok
In the ActiveMQ doc http://activemq.apache.org/exclusive-consumer.html it
states
The broker will pick a single MessageConsumer to get all the messages for a
queue to ensure ordering. If that consumer fails, the broker will auto
failover and choose another consumer.
Is this a consumer master slav
Thanks for the prompt and helpful reply
Tony
--
View this message in context:
http://old.nabble.com/JDBC-Master-Slave-Cluster-question-tp28288022p28288026.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
I am looking into clustering ActiveMQ brokers, the Master and Slave approach
seems the best approach.
One Master one or more slaves depending on the cluster.
I have discounted the pure master slave since to restart the master you have
to take the slave down.
So I am looking at the JDBC Master S
