Thanks for your answer. The message conversion scenario is trivial. Shorter scenario is that:
Site A produces a message X and sends it to site B. If all of the clusters on site B fail, site A will send the message to site C. My scenario looks like B1 B2 B3 C1 C2 C3 are backup servers in that order but only for the message X. Site A sends some other messages than X directly to the site C. So for other messages's point of view, C clusters are not backup of B clusters. Normally I was planning to use netty and manage the connections as I described. Normally i am doing failover over connections. For reliable messages I was planning async Acks. For some cases duplicate detection requires. Then I have heard hornetq and then artemis which does nearly all of my requirements. I dont want to reinvent the wheel. But I cannot figure not the queues, the bridges, the diverts, the cluster groups required. Especially site B to site C failover is very likely to the artemis solution. But it is something cülike clusters of clusters -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776p4703798.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
