-
1. Re: Issue with Duplicate Message Detection
timfox May 4, 2010 4:31 AM (in response to jbmuser)Does this happen with TRUNK?
If so, can you provide some test code?
-
2. Re: Issue with Duplicate Message Detection
jbmuser May 4, 2010 5:54 AM (in response to timfox)Hi Tim,
I didn't try with trunk yet, but I am able to reproduce this with 2.0.0.GA
Please see attached test.
1) Update server url in DuplicateMessageTest.java
2) Update jmxPort in HornetQSender.java and HornetQReceiver.java
3) Run DuplicateMessageTest.java
Thanks
Bijith
-
src.zip 4.8 KB
-
-
3. Re: Issue with Duplicate Message Detection
jbmuser May 4, 2010 5:59 AM (in response to jbmuser)Also, I noticed that, usually when duplicate messages are detected, server logs a warning as shown below, but when I run the atached test, there are no such warnings in server.
[New I/O server worker #1-1] 15:14:03,160 WARNING [org.hornetq.core.postoffice.impl.PostOfficeImpl] Duplicate message detected - message will not be routed
-
4. Re: Issue with Duplicate Message Detection
timfox May 4, 2010 6:09 AM (in response to jbmuser)Can you attach a self contained JUnit test? It's a lot easier for us to run.
You can adapt one of the duplicate detection tests from the source.
-
5. Re: Issue with Duplicate Message Detection
timfox Jul 6, 2010 4:53 PM (in response to timfox)It doesn't mean the server rejected the messages.
When using paging, paged messages are *not in the queue* so they won't show up on the queue message count.
The paging store is a separate staging area before messages are routed to queues.