Did you get solution? I got similar issue and post at
http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-after-failover-td4719934.html
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Unmatched-acknowledge-MessageAck-start-of-ack-in-XA-transaction-initiated-by-O
On Thu, Feb 9, 2017 at 3:54 PM, Francesco PADOVANI <
francesco.padov...@bticino.it> wrote:
> Hi Martyn,
>
> Thanks a lot for this!
>
> It could save us just in time...
I hope so.
>
> As soon as I can, I'll try to build artemis from your last commit and make
> some tests.
>
I've created a snapsho
Hi Martyn,
Thanks a lot for this!
It could save us just in time...
As soon as I can, I'll try to build artemis from your last commit and make some
tests.
I'll give you a feedback.
Francesco
From: Martyn Taylor
Sent: Thursday, February 9, 2017 1:22:52 PM
To
Did Old Gen continually increase *after* performing full GCs? That is, was
the Old Gen usage after full GC #N always greater than the Old Gen usage
after full GC #N+1? If not, you were concerned about something that doesn't
matter.
It's OK for Old Gen to grow; that's why we have a garbage collecto
Francesco,
I think I've identified the cause of this problem. There were two issues
which are now fixed as part of:
https://github.com/apache/activemq-artemis/pull/1002
I'll get these fixes cherry-picked onto Artemis 1.x stream.
I plan on doing a 1.5.3 (with these changes included) within the n
