activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: JDBC Master Slave
Date Tue, 12 Dec 2006 16:30:05 GMT
On 12/12/06, Anthrope <pn@anthrope.com> wrote:
>
> James,
>     Thanks for the response. I am using the config file as-is from the
> example. I am using the jdbcPersistenceAdapter element, and here's what I
> have:
>
> - I start activemq on port 5616 and it duly starts up, taking over as the
> master
> - I start a second instance with exactly the same configuration, and it
> fails to start, because it tries to bind to 5616
> - I change the configuration to use port 5626,

This sounds like something is not working correctly as a slave should
not try to bind to a socket until it becomes the master.

> - I don't quite understand how both end up becoming the master, but perhaps
> it's just how it's being logged?

No - sounds like you're not using a shared database between the two.


> - I kill the master broker and then run the consumer example with the
> failover uri and am able to successfully extract about 7800 messages before
> the client shuts down with a JMS exception

What exception?

-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message