Hi,
I'm working on ActiveMQ 5.8.0 with MySQL as a data source. The configuration
of ActiveMQ is attached (activemq.xml). It is used in a basic scenario: a
producer sends a short message (JSON object with 2 fields) with 5s delay to
queue T on which 3 consumers listen. The consumers are created
enable TRACE level logging, it will give more information.
it seems that the message audit on the cursor may see the second
scheduled message as a duplicate. The audit is
not persisted so it would explain why a restart helps.
Using a destination policy entry, disable the message audit:
Hi,
adding enableAudit=false in policyEntry works like a charm. Thanks a lot!
Having known it's enableAudit's responsibility I found an article describing
a similar problem to mine:
http://tmielke.blogspot.de/2012/03/i-have-messages-on-queue-but-they-dont.html
.
Cheers,
Tomek
--
View this
