[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-604) Duplicate message detection

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-604?page=comments#action_12414399 ] 
            
Tim Fox commented on JBMESSAGING-604:
-------------------------------------

the replication approach removes the possibility of duplicate messages on send, but if there is only one server in cluster, and it fails, and is brought up and client retries then can still get duplicates - need to implement duplicate detection for this too.

> Duplicate message detection
> ---------------------------
>
>                 Key: JBMESSAGING-604
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-604
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>             Fix For: 2.0.0 Beta
>
>
> Whereas JMS requires once and only once *delivery* of messages, there are no such guarantees when sending messages to a queue/durable sub.
> This can result in duplicate messages existing in a queue or durable sub.
> For some clients this is unacceptable, so we should implement a feature which alerts to the presence of duplicates.
> This can be done by keeping a persistent cache of message (or transaction) id on the server. Entries should time out after a period of time.
> This will not remove duplicates 100% of the time since we cannot cache the previous values of id for ever, but only for a window.
> See forum thread for more details

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira