[
https://issues.apache.org/jira/browse/AMQNET-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remo Gloor updated AMQNET-462:
------------------------------
Description:
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 dupplicate 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.
was:
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
> 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 dupplicate 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)
