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 18:15:00 GMT

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

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

bq. I want to use the same ID because they are exactly the same message.

I'm a bit confused. In the issue description you said, "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." If the person's address is updated does that not mean that the
contents of the message you're sending is different than the previous message (i.e. the new
message contains a different, updated address)? Perhaps that's not the way your application
is designed, but it's not clear from your description. Please clarify.

bq. The only problem is the first message was consumed already...

What should happen if the first message *wasn't* already consumed. Should the new "update"
message be considered a duplicate in that case and ignored?

In what case should duplicate detection actually ignore messages in your application?  It
seems like sometimes you want it to detect duplicates and sometimes you don't, but the specifics
of each case is not clear.

bq. ...wouldn't being able to configure it to delete ID from the cache on delete/consume from
the queue make it more flexible?

Technically speaking it would make it more flexible, but flexibility in itself isn't a good
enough reason to implement such a change as flexibility also increases complexity (which increases
the chance of bugs) and reduces maintainability.  I still don't understand your use-case enough
to know why the existing duplicate detection wouldn't work for you.

> 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