activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-462) Failover transport: Deduplication algorithm is wrong (1)
Date Thu, 14 Nov 2013 14:23:34 GMT

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

Timothy Bish commented on AMQNET-462:
-------------------------------------

A unit test for this would be a good start.

> 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)

Mime
View raw message