Ah - ok,
master/slave doesn't handle this scenario - it is designed to provide
a simple backup-support. When you wish to re-enable a master, you
will need to ensure that the master is up to date with the slave -
this is a manual process:
1. stop the slave
2. copy the data directories from the slave broker to the master.
3. re-start master then slave brokers.
cheers,
Rob
On 22 Mar 2006, at 12:07, Javier Leyba wrote:
On 3/22/06, Rob Davies <[EMAIL PROTECTED]> wrote:
When you say you restarted the master - was the slave still running
and which broker was the listener attached (master or slave) ?
On 3/22/06, Rob Davies <[EMAIL PROTECTED]> wrote:
When you say you restarted the master - was the slave still running
and which broker was the listener attached (master or slave) ?
Rob
Yes, slave was running and I don't know wich broker listener were
attached because I'm using failover as follows:
----------
ActiveMQConnectionFactory connectionFactory =
new
ActiveMQConnectionFactory("failover://(tcp://
172.31.112.9:62002,tcp://172.30.27.1:62003)?
randomize=false&connectionTimeout=20000&soTimeout=10000&wireFormat.max
InactivityDuration=20000");
------------
Thanks in advance
J
