Does this happen with TRUNK?
If so, can you provide some test code?
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
src.zip 4.8 KB
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
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.
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.