:
>
> Message Groups are a feature used within a single broker to implement
> sticky load balancing across consumers. They are not intented as a way
> to load balance across brokers.
>
> My recommendation would be to use one of the Master/Slave approaches
> with Messag
I'm testing a HA configuration, using activeMQ 4.1.1. I have two brokers and
a client sending messages with failover between the brokers. I tried using
the message groups feature to ensure that messages always went to the same
broker, unless that broker failed. This works well ... very cool featur
L, TTIME BIGINT, BROKER_NAME
VARCHAR(250), PRIMARY KEY (ID) );
>From there on it seems to work.
Pete
James.Strachan wrote:
>
> On 4/6/07, prylance <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I'm using Oracle TimesTen embedded database
>> (http://www.or
Hi,
I'm using Oracle TimesTen embedded database
(http://www.oracle.com/technology/software/products/timesten/index.html) and
want to use it as the persistent message store with ActiveMQ. It isn't
mentioned in the ActiveMQ list of supported JDBC databases:
http://activemq.apache.org/jdbc-support.
Hi,
I read and followed the how-to's on integrating activeMQ with JBoss:
http://activemq.apache.org/jboss-integration.html
http://devzone.logicblaze.com/site/integrating-apache-activemq-with-jboss.html
... very good, clear, and worked for me. Thanks. One question though ...
I'm using activ
