Ok, on that case the I'm sending a result shortly. On Thu, Sep 6, 2018 at 12:36 PM Justin Bertram <[email protected]> wrote: > > That's correct, Michael. Additionally, I've found that the current logic > for updating the addresses & queues causes a catch-22 where the address > can't be updated until the queue is updated and vice-versa. Something > fundamentally more clever will be required for this use-case. I'll let you > have a crack at it, Michael, while I work on a few other things in the > mean-time. > > > Justin > > On Thu, Sep 6, 2018 at 11:27 AM, michael.andre.pearce < > [email protected]> wrote: > > > Ive been looking at the routing type issue. And why the original issue is > > there. > > There isnt actually any issue in the queueUpdate logic that exists already > > for routetype. > > The issue is before that, where addressinfo update is erroring as trying > > to update it route type but the queue hasnt been updated and that throws > > exception meaning it doesnt get to queue update. Its relatively simply to > > fix. Ill try send a pr. > > > > And yes heres a +1 if were all on board with fixing that a different way > > > > > > Sent from my Samsung Galaxy smartphone. > > -------- Original message --------From: "michael.andre.pearce" < > > [email protected]> Date: 06/09/2018 17:23 (GMT+00:00) To: > > [email protected] Subject: Re: [VOTE] Apache ActiveMQ Artemis 2.6.3 > > Clebert the pr you tag here is for a seperate feature. > > That particular pr is adding similar updateability for filter but avoids > > the very issue here. > > > > > > Sent from my Samsung Galaxy smartphone. > >
-- Clebert Suconic
