[
https://issues.apache.org/jira/browse/AMQNET-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822481#comment-13822481
]
Remo Gloor commented on AMQNET-462:
-----------------------------------
My unittest and fixes for this problem rely other patches that are not applied
since 9 months. I won't spend the time to reduce them to the current trunks
version and separate the various problems from each other into small patches
because I have the feeling that my help isn't really apprechiated and there is
little to know guarantee that such patches will be applied anyway. So it's just
waste of time. This is just to tell you that you have a problem. I fixed it for
myself already.
Applying patches that are open for 9 months would be a good start to work
together from your side.
> Failover transport: Deduplication algorithm is wrong (1)
> --------------------------------------------------------
>
> Key: AMQNET-462
> URL: https://issues.apache.org/jira/browse/AMQNET-462
> Project: ActiveMQ .Net
> Issue Type: Bug
> Reporter: Remo Gloor
> Assignee: Jim Gomes
>
> 1. Create and start consumer
> 2. Messages are delivered and queued in unconsumed messages
> 3. Listener is added
> 4. Messages are Redispatched
> 5. Messages are considered duplicates
> Succestion:
> Have a cleare state of messages in the unconsumed messages. Either they
> should be in the connections duplicate list or not.
> If they are in the in the dup list. then rollback dup whenever a message is
> redispatched.
> If not check dup before deliver to message to the client. (Receive/Deliver to
> Listener)
> This makes it much easier to get a correct code then currently where
> unconsumed messages can either be in the dup list or not.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
