[jira] [Closed] (ARTEMIS-3389) send message with rollback won't allow duplicate detection to happen again

["Clebert Suconic (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-3389.
------------------------------------
    Fix Version/s:     (was: 2.18.0)
       Resolution: Won't Fix

Even though this would be my preferred semantic on duplicate-detection. there are tests validating exactly this case.. that a duplicate detection is only registered after a commit.

 

Since TX is the thing supposed to control the duplication really, I think on this case it makes sense now that I think about it.


I am rejecting this as probably Wildfly has tests validating this semantic...

So, I'm rejecting my own idea here.

> send message with rollback won't allow duplicate detection to happen again
> --------------------------------------------------------------------------
>
>                 Key: ARTEMIS-3389
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3389
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> There is another issue around this as well. 
> if one thread sent the message, TX still pending, another producer send it... both will go through.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)