[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-604) Duplicate message detection
[ http://jira.jboss.com/jira/browse/JBMESSAGING-604?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-604:
-------------------------------------
There will always be the possibility that duplicate messages can be received until we
implement duplicate message detection.
Consider the following possibility:
A message is sent the send succeeds on the server
The message is delivered to the client and acked.
The ack removes it from the server
The server then fails *before* the original send message has written its response to the
socket
The client receives a socket exception
Failover kicks in
After failover the client resumes the send
The message gets delivered again
And yes, this was actually seen to happen in the logs :)
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: 1.2.1
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