Sambit, we gave up doing it this way. We have tried JBossMQ too, but we faced
very similar persistence issues, so we arrived at the conclusion that JMS
itself was not a very good choice to manage the nodes of a cluster. We've
ended up using JGroups to implement an IP-multicast based cluster manage
Why do you need more than one broker BTW? A single broker can happily
load balance messages across a cluster of MDBs. For HA use a pair of
Master/Slave brokers
On 6/22/07, sambit <[EMAIL PROTECTED]> wrote:
Hi Thiago,
We were also trying to use a similar set up with Jboss and ActiveMQ
Embedded
Hi Thiago,
We were also trying to use a similar set up with Jboss and ActiveMQ
Embedded broker. We are facing same issues as you have mentioned. I'm
wondering could you finally able to resolve this and can you suggest what is
the best practice to use ActiveMQ broker, Jboss, MDB for a highly scal
