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

Tim Fox (JIRA) jira-events at lists.jboss.org
Mon Feb 2 15:22:44 EST 2009


     [ https://jira.jboss.org/jira/browse/JBMESSAGING-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox closed JBMESSAGING-604.
-------------------------------

    Resolution: Done


> Duplicate message detection
> ---------------------------
>
>                 Key: JBMESSAGING-604
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-604
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>            Assignee: 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list