aconway.rh wrote
> On Mon, Apr 16, 2018 at 8:52 AM, Gordon Sim <

> gsim@

> > wrote:
>> No. The problem is that a transaction could involve messages to/from
>> different brokers, i.e. the transaction would become a distributed
>> transaction. At present there is no support for that in the router.
> We talked before about this: the idea was to start a non-distributed TX
> based on the first broker involved, and abort it if it attempts to spread
> to more brokers. However this approach would really create a lot of
> potential for error and confusion, as well as complexity in the router.
> The
> conclusion was that such a partial solution would probably do more harm
> than good, and if we want to move towards multi-broker TX we should put
> our
> effort into proper standard distributed TX and not some halfway solution.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: 

> users-unsubscribe@.apache

>> For additional commands, e-mail: 

> users-help@.apache


Agree with that one; a proper distributed TX would indeed be the best
solution; Couldn't find any issue in the Jira, are there plans to build
this? I think it would be a great addition.

Sent from:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to