Hi,
As you talk about an external loadbalancer, I guess that you're going to
loadbalance HTTP requests.
Which version of ServiceMix do you expect to use ?
Anyway, in ActiveMQ, to share the same persistence adapter (in the
activemq.xml), you can use:
- a NFS mount share in all ActiveMQ nodes using a file adapter:
<amq:persistenceAdapter>
<amq:amqPersistenceAdapter directory="file:/nfs/mount/data"/>
</amq:persistenceAdapter>
- a "clean" solution is to use a journaled JDBC persistence adapter
<amq:persistenceAdapter>
<amq:journaledJDBC journalLogFiles="5" dataDirectory="/data/"
dataSource="#jdbcDataSource"/>
</amq:persistenceAdapter>
A killer feature in ActiveMQ 5.3.x is the Kaha backend. I never tried
this configuration in a multi-nodes configuration, but you can try:
<amq:persistenceAdapter>
<amq:kahaPersistenceAdapter directory="activemq-data"
maxDataFileLength="33554432"/>
</amq:persistenceAdapter>
Regards
JB
On 05/06/2010 03:57 PM, ssheth wrote:
We are going to use an external loadbalancer before a request hits ServiceMix
running on three different machines. This configuration doesn't require us
to configure SM in a cluster or in HA mode. How do we ensure that ActiveMQ
Brokers talk to same persistenace store without configuring SM instances in
Master Slave mode? Do we stop default ActiveMQ broker in SM instances and
use broker on external ActiveMQ configured as Master Slave?
