Another way is just not to care about dupes from producers and instead
focus on the consumer via the idempotent receiver enterprise integration
pattern[1] since you probably want do that anyway if you want to be sure
not to process the same message multiple times.
As long as the producer uses a
To my knowledge, ActiveMQ "Classic" doesn't support detecting duplicate
messages from producers. You might consider using ActiveMQ Artemis if you
want that feature.
Justin
On Wed, Jun 1, 2022 at 1:35 PM Gunawan, Rahman (GSFC-703.H)[Halvik Corp]
wrote:
> The broker detecting duplicates from
On 2022/06/01 18:15:24 "Gunawan, Rahman (GSFC-703.H)[Halvik Corp]" wrote:
> Hi,
> Does ActiveMQ 5.15.4 have duplicate message detection? If yes, where can
I find the documentation?
>
> Thanks
>
> Regards,
> Rahman
>
Hello Justin,
Thank you for your response and sorry for the delay is this follow-up.
Regarding your response:
> I'm not aware of such a production deployment and I would be surprised if
> there was one given that clustering was designed for local area networks with
> low latency which
The broker detecting duplicates from producers.
Thanks
Rahman
-Original Message-
From: Justin Bertram
Sent: Wednesday, June 1, 2022 2:30 PM
To: users@activemq.apache.org
Subject: [EXTERNAL] Re: ActiveMQ 5.15.4 duplicate message detection
What's the use-case? Are you talking about the
What's the use-case? Are you talking about the broker detecting duplicates
from producers or consumers detecting duplicates from the broker?
Justin
On Wed, Jun 1, 2022 at 1:16 PM Gunawan, Rahman (GSFC-703.H)[Halvik Corp]
wrote:
> Hi,
> Does ActiveMQ 5.15.4 have duplicate message detection?
Hi,
Does ActiveMQ 5.15.4 have duplicate message detection? If yes, where can I
find the documentation?
Thanks
Regards,
Rahman
Thank you Justin. This was very helpful. No further questions.
Aaron Steigerwald
-Original Message-
From: Justin Bertram
Sent: Thursday, May 26, 2022 12:41 AM
To: users@activemq.apache.org
Subject: Re: [EXTERNAL]:Re: Journal corruption caused by split brain?
[CAUTION: This email
I will address the issues you faced on mirroring.
it's definitely new functionality but it's a hot topic.. we should
address the issues.
The issue with the Expiry is that message was moved once on the main
broker.. then moved again on the target causing the duplicate.
and the statistics..
Thanks for elaborating! Those are all fair points about broker mirroring
vs. DB replication.
Moving from JBossMQ to ActiveMQ Artemis should be a major step up in both
performance and features even with the continued use of JDBC. Also, I don't
think JBossMQ has seen any maintenance of any kind for
Both the client code and broker configuration look fine to me. It seems
pretty clear that the problem is environmental.
Justin
On Wed, Jun 1, 2022 at 3:47 AM Sunil Varma wrote:
> Ok Let me attach again.The attached zip file contains both broker.xml
> and ArtemisHTTPDebug.java
>
> On Tue, 31
I’m not on the DBA team so I don’t know specifics but it is asynchronous
replication to a secondary server in the same datacenter and a similar
primary/secondary server to the standby datacenter.
Theoretically the mirroring in Artemis should offer the same resiliency
(synced to the disk, possibly
Ok Let me attach again.The attached zip file contains both broker.xml and
ArtemisHTTPDebug.java
On Tue, 31 May 2022 at 16:53, Justin Bertram wrote:
> Your second email in this thread is the only email with any attachments,
> and it has 3:
>
> - local-server-log-snippet.txt
> -
13 matches
Mail list logo
