You want your master slave to use "master/slave"
then you tell your clients about the failover, also look at these pages:
http://activemq.apache.org/masterslave.html
http://activemq.apache.org/jdbc-master-slave.html (Since you mentioned DB2)
http://activemq.apache.org/shared-file-system-master-s
That goes in the clients connector.
On May 12, 2011, at 12:28 AM, archa wrote:
> Can you tell me where exactly to mention the failover syntax.
> Eg:
> failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false
>
> Should this go in the transportconnector tag ?
>
> --
> View this mess
Can you tell me where exactly to mention the failover syntax.
Eg:
failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false
Should this go in the transportconnector tag ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Native-Clustering-in-ActiveMQ-tp3516488p35
Oh,
Yes, then you are on the right track.
ActiveMQ supports 3 models.
Memory (Don't use this)
Disk (Use this for speed, niceness and whatnot else)
JDBC (It'll be slow)
/je
On May 11, 2011, at 11:06 PM, archa wrote:
> My requirement is as follows:
>
> I have my application which currently wri
My requirement is as follows:
I have my application which currently write to a single broker queue.
Incase the broker goes down, my messages are lost, till I restart the broker
and the consumers again (as consumers are formed on application startup).
To avoid the loss of messages, I want sort of
Clustering so to say kinda sorta goes against the JMS
spec, the idea is to get messages from A->B as quickly as possible.
There are HA solutions for stability and you can use networks
of brokers to provide scalability but the idea of "clustering" messages,
i.e replicating messages stores is kinda
