I'm a bit confused by your message... Are you describing the scenario you need and wanted to make sure it works?
Or are you implementing something that converts a message and then move to the other site? We have a JIRA open to support datacenter failover.. which is not currently implemented. I think There are ways to achieve that without implementing anything on the code, but we don't have anything for that such as replicating remotely, etc.. It's hard to do these things and keep transactional guarantees that are required by JMS use cases. .(that's the main reason why this wasn't implemented)... and doing that without adding latency is a tricky thing. If you add some extra detail here on what you mean, I could help out more. On Mon, Nov 9, 2015 at 3:32 AM, bosbeles <[email protected]> wrote: > Hi. I have problems on designing message queue oriented design on a clustered > fault tolerant system. > > There are three sites A B C. > > B is clustered as B1 B2 B3. > > C is clustered as C1 C2 C3. > > A message X (1000-5000 Xs per second actually) is sent to B cluster from > Site A. > > B converts it to Y and sends it to C. > > C converts it to Z and sends it to B. > > If the connection between A and B fails A sends X to C. Now C converts it to > Z and sends Z to B. > > If all connections of A fail then A stores Xs locally. > > I have looked at the Apache Activemq Artemis. > > But i cannot exactly figure out whether it fulfils my above scenario. > > Could you help me? Thanks for your answers. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Artemis-message-queue-oriented-design-help-tp4703776.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Clebert Suconic
