activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1755) Delete message from duplicate cache on message consume
Date Tue, 20 Mar 2018 19:02:00 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406870#comment-16406870
] 

Justin Bertram commented on ARTEMIS-1755:
-----------------------------------------

Thanks for the clarification.

bq. By updated message, I meant some other metadata associated with the same ID being updated
and that metadata is not present in the message. That's why I'm using same _AMQ_DUPL_ID on
both messages.

Instead of using the same duplicate ID could your application not set a different one in this
case assuming it knows the data in question has been updated and therefore is semantically
different?

I still see this as an application issue.  It should have the information to determine whether
or not a message really is semantically a duplicate or not and should set the duplicate ID
accordingly.

Aside from that, have you looked at [last-value queues|https://activemq.apache.org/artemis/docs/latest/last-value-queues.html]?
 The semantics are different from what you're looking for, but you might be able to use it
instead somehow.  What you actually want is what I would call a "first-value queue" which
is the opposite of a last-value queue.  I think a "first-value" queue would be a better feature
than a change to duplicate detection.

> Delete message from duplicate cache on message consume
> ------------------------------------------------------
>
>                 Key: ARTEMIS-1755
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1755
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.4.0
>            Reporter: Rini Bollarapu
>            Priority: Minor
>              Labels: newbie
>
> Hi, duplicate cache still contains the message even if the message was consumed from
the queue or deleted from the queue. From the documentation, it looks like there's no configuration
to handle something like this. 
> Example:
> A message containing a person's information is sent to a queue and consumed. After sometime,
the person's address is updated and the update message is sent to queue. This updated message
is ignored as a duplicate because the original message was not removed from the duplicate
cache when it was consumed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message