No problems, Gary, and I appreciate your input.
I've created
https://issues.apache.org/jira/browse/ARTEMIS-3693
-Original Message-
From: Gary Tully
Sent: Thursday, 17 February 2022 9:53 PM
To: users@activemq.apache.org
Subject: Re: Artemis duplicate detection
apologies, I must
ay, 16 February 2022 8:45 PM
> To: users@activemq.apache.org
> Subject: Re: Artemis duplicate detection
>
> The fix in
> https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FARTEMIS-3521&data=04%7C01%7CBrad.Harvey%40gbst.com%7Cead9bfe
From: Gary Tully
Sent: Wednesday, 16 February 2022 8:45 PM
To: users@activemq.apache.org
Subject: Re: Artemis duplicate detection
The fix in
https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FARTEMIS-3521&data=04%7C01%7CBrad.Har
ld result in this
> property being set under the covers when sending a message?
>
>
> Background:
>
> I ran into issue where artemis' duplicate detection triggered, causing
> transaction rollback. I say unexpected because we don't set the duplicate
> detection header
_ID header on the consumed message which is
available to the client to read (2). Is there anything in the activemq classic
openwire or qpid jms amqp libraries that would result in this property being
set under the covers when sending a message?
Background:
I ran into issue where artemis&
