How do you know the messages aren't getting consumed? What test are you using to know that they're unconsumed? There seem to be bugs in the code that increments/decrements message counts (some users report negative counts, which should only happen on occasion as a race condition), so if you're only looking at the web console, you might not actually have unconsumed messages. Can you browse them via the web console?
Tim On Jul 6, 2016 5:58 AM, "Christopher Shannon" < christopher.l.shan...@gmail.com> wrote: One thing you might want to try is a newer version. Off the top of my head I can't remember if any bug like this was already reported but there have been a ton of fixes since 5.10.0. On Wed, Jun 29, 2016 at 4:36 AM, Kamal Vaddadi < kamal.vadd...@trilliantinc.com> wrote: > > We have noticed that, when running with high throughput, a small fraction > of > messages are not getting consumed even though the consumers are active. > These messages are remaining forever in a queue until broker is restarted. > > > Does anyone know in what circumstances this can happen and how to diagnose > and ideally avoid it? We are using > > ActiveMQ: version 5.10.0 > Database: Oracle > JVM: 1.8 > Queue Type: persistent > > > Thank you > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/A-small-fraction-of-messages-remaining-in-queue-forever-tp4713429.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
