-
1. Re: Duplicate message detected but identifier is unique
ataylor Oct 30, 2012 11:25 AM (in response to chrisabaird)I cant see how this caan happen, your sure your backup is actually a backup and you arent seeing the message re distributed, ive seen cases where this happens with 2 live servers and the message ends up back where it started.
-
2. Re: Duplicate message detected but identifier is unique
clebert.suconic Oct 30, 2012 11:33 AM (in response to chrisabaird)what TX Mode are you using?
once the duplicate is detected the whole transaction will be ignored.
-
3. Re: Duplicate message detected but identifier is unique
chrisabaird Oct 30, 2012 12:02 PM (in response to clebert.suconic)Replying to both of you --
Thanks, Andy. I did check and confirm that my backup is a backup. I also looked to see if any failover happened and none has.
Clebert, I created my session with "false" for the transacted boolean and AUTO_ACKNOWLEDGE for the acknowledgement mode. I've also set the session to use a custom send acknowledgement handler. The sendAcknowledged method is empty on the handler.
Thanks for helping
-Chris
-
4. Re: Duplicate message detected but identifier is unique
chrisabaird Oct 30, 2012 3:28 PM (in response to chrisabaird)Sorry, more info that I realize I wasn't clear on.
I'm running on 2 servers. Each server has
- Primary HornetQ
- Backup HornetQ
- Producer (Java service of my own)
- Consumer (Java service of my own)
The HornetQ primary and backup use a broadcast group and a discovery group. The group-address and group-port is the same for broadcast and discovery and the same in all 4 configurations (both primary and both backup). Some other configuration notes
- <use-duplicate-detection>true</use-duplicate-detection>
- <forward-when-no-consumers>false</foward-when-no-consumers>
Thanks
-Chris
-
5. Re: Duplicate message detected but identifier is unique
clebert.suconic Oct 30, 2012 6:05 PM (in response to chrisabaird)You only have a primary and backup server? or you have other nodes?
if you have more than one node, there's an issue with redistribution when using duplicate detection which I'm by coincidence (not related to this issue) working on at the moment:
https://issues.jboss.org/browse/JBPAPP-10296
(post edited by Clebert.. had a wrong link here before)
-
7. Re: Duplicate message detected but identifier is unique
clebert.suconic Oct 30, 2012 6:57 PM (in response to clebert.suconic)I just sent a PR for this:
https://github.com/hornetq/hornetq/pull/640
https://github.com/hornetq/hornetq/pull/639
https://github.com/hornetq/hornetq/pull/638
I"m not sure if it's the issue you're facing.. but it's the closest I could get so far.