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 Persistence
Date Fri, 24 Mar 2006 22:53:32 GMT
On 3/24/06, Jack Humphrey <jackh@google.com> wrote:
> If I'm running on ActiveMQ 3.2.2 then master/slave is not an option, correct?

Yes

> I'm using 3.2.2 and the reliable: transport. Is the "randomize=false"
> argument available to make sure that I usually hit my master broker?
> How do I achieve the "locking out" that you refer to?
>
> Also, in some testing I did with 3.2.2, it seemed that if journaling
> was disabled, and the database became unavailable (simulating mysql
> crash), that incoming messages were just lost. Does that sound like
> what you'd expect? I can debug further if that surprises you.

We should be failing the send() call in those cases

--

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

Mime
View raw message