Yep. That will work.
I would keep load balance off on my system. Producers and consumers equally distributed. But I will fix this asap. (1 or 2 weeks) On Tue, Jul 18, 2017 at 8:36 PM Dan Langford <danlangf...@gmail.com> wrote: > Oh great this is good news. Good in that I'm not crazy and completely inept > and you guys are aware of the situation. I'll make a jira ticket here in a > bit. From our point of view a message is a message is a message while it's > in Artemis and amqp vs core is just a distinction on how one might get a > message in or out. I understand, now more fully, that it's not as straight > forward as that. > > Let me help you understand why this is quite important to us: our > enterprise already uses some AMQP (Qpid) and the .Net support for AMQP is > quite nice with servicebus hitting the scene. So we would love to maintain > the idea of clients using existing patterns around AMQP. We were hoping for > an Artemis cluster primarily for the message replication. Something that > doesn't seem to come as cleanly with ActiveMQ Kaha MasterSlave or with > QPID. > > If I disable load balancing on the Artemis cluster (and go to QDR for that) > can I expect to still be able to enable ha colocation replication? Will it > be able to replicate AMQP messages ok? > > Thanks > On Tue, Jul 18, 2017 at 6:00 PM Clebert Suconic <clebert.suco...@gmail.com > > > wrote: > > > > That message bridge is meant for core messages, and right now an > > > AMQPMessage would be converted to Core Message and you would receive > > > it as core message on the other side. > > > > > > > > I meant.. if it was working at all.. so I need some work on this. > > hence the 2 weeks. > > > -- Clebert Suconic
