Hi Jack-
This looks like you are using the JDBC backend. I would recommend having the
DBA review logs for the database for other indicators. You may have a couple
things going on. For sure it appears you have a duplicate publishing attempt
based on the PRIMARY KEY violation.
-Matt Pavlovich
Hello Jack,
clear thanks.
But are you able to reproduce the issue sistematically? If yes, in theory,
if you restart the slower broker instance and you let it get the lease
again (e.g. shutting down all the others), it should flush in the shared
datastore the still pending messages it has still
Hi Marco,
Thanks for getting back to me, we're really scratching our heads over this one.
The second log frame is on a different broker to the first log frame.
We assume the first broker is creating the record but not sending the message,
then the second broker cannot create the record and
> Thanks
>
> -Original Message-
> From: Jack Fry (They/Them)
> Sent: Monday, February 12, 2024 4:16 PM
> To: users@activemq.apache.org
> Subject: RE: Message delivery failure and Primary Key violation on load
> balanced ActiveMQ Broker
>
> [You don't often get ema
classic v5.18.3 and these failovers started not long
after upgrading from v5.13.2.
Thanks
-Original Message-
From: Jack Fry (They/Them)
Sent: Monday, February 12, 2024 4:16 PM
To: users@activemq.apache.org
Subject: RE: Message delivery failure and Primary Key violation on load
Looking at the logs again, we noticed this warning on the broker as well:
Store limit is 30720 mb (current store usage is 0 mb). The data directory:
D:\Apps\apache-activemq-5.18.3\data only has 25672 mb of usable space. -
resetting to maximum available disk space: 25672 mb
Could this be
