If the dequeue count is staying at 0, then this isn't a performance problem, and you can ignore that portion of my earlier email in this thread.
It sounds like something's not right, either with your code or with ours. Can you please post the consumer code you're using, so we can see if there's anything obvious about it that might need to change? Also, can you please attach a debugger to your consumer process and set a breakpoint on the call to acknowledge() and confirm that it's actually being called? (If some branch in the code caused you to miss that call, that would explain everything.) Tim On Jul 15, 2017 8:02 PM, "akpuvvada" <akp4ti...@gmail.com> wrote: > When I tried multithreaded (processing parallel) the subscriber is not > logging any receipt. That made me affectively conclude it is not processing > any messages. However, when I tried single thread (serial processing) I can > see the subscriber is updating the log; so I know it is receiving the > messages and sending back acknowledgement . However, in the Active MQ UI, I > can see that all messages are in pending state and dequeued is 0. > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Active-MQ-Performance-with-CLIENT-Ack-tp4728551p4728578.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
