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

Rini Bollarapu commented on ARTEMIS-1755:
-----------------------------------------

{quote}Aside from that, have you looked at [last-value 
queues|https://activemq.apache.org/artemis/docs/latest/last-value-queues.html]?
{quote}
Last-value queues is an awesome feature! Thanks for the link, I haven't looked 
at that before. These queues work for my application. But I observed that 
last-value queues do not remain last-value queues on broker restart. I can 
confirm this from the queues information shown in the web-console, the 
last-value check box is not checked after restart. May be I need to open 
another issue for this if there isn't one already.
{quote}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.
{quote}
Yes, first-value queue would be better than changing 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)

Reply via email to