On 2/8/07, spiderman2 <[EMAIL PROTECTED]> wrote:
I've read about the shared database (known to be slow) and shared file
system, SAN, (quite expensive HW). But where can I read about replicating
messages.
The 'Pure Master Slave' is the third option...
http://activemq.apache.org/masterslave.html
I've read about the shared database (known to be slow) and shared file
system, SAN, (quite expensive HW). But where can I read about replicating
messages. I was under the impression that Brokers currently do *not*
replicate messages under a Network Of Brokers scenario. Only a M-S scenario.
How ca
On 2/8/07, spiderman2 <[EMAIL PROTECTED]> wrote:
But I'm concerned with respect to scalability. I'm assuming the Network of
Brokers was created such that the deployment could scale to a large number
of consumers.
A single broker can easily handle many thousands of consumers.
What kind of sc
But I'm concerned with respect to scalability. I'm assuming the Network of
Brokers was created such that the deployment could scale to a large number
of consumers. What kind of scalability issues/limits will I have with a
Master/Slave scenario?
Thanks!
Shawn
James.Strachan wrote:
>
> Yes, Ma
On 2/8/07, James Strachan <[EMAIL PROTECTED]> wrote:
Yes, Master/Slave is the answer for high availability and to avoid
message loss if a broker dies.
Slight correction - killing and restarting a regular broker with
persistent messaging will not loose messages. Its if you loose the box
on which
Yes, Master/Slave is the answer for high availability and to avoid
message loss if a broker dies.
On 2/7/07, spiderman2 <[EMAIL PROTECTED]> wrote:
Hi,
I'm a New user. I'd like to use activemq for a Network Of Brokers /
Clustered deployment. The catch is that I can't afford to loose a single
m
