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
(They/Them)
Sent: Monday, February 12, 2024 2:35 PM
To: users@activemq.apache.org
Subject: Message delivery failure and Primary Key violation on load balanced
ActiveMQ Broker
[You don't often get email from j...@scottlogic.com.invalid. Learn why this is
important at https://aka.ms
this be related? If there was not enough available disk space would It
cause this exception to occur?
-Original Message-
From: Jack Fry (They/Them)
Sent: Monday, February 12, 2024 2:35 PM
To: users@activemq.apache.org
Subject: Message delivery failure and Primary Key violation on load balanced
(Re-sent this as I wanted to change the subject)
Hi,
Last week our ActiveMQ message broker lost a message from the queue. We have a
load balanced system with two separate brokers sharing a data store. At some
point during the transfer of the lease, the original lease holder started
shutting
