I am using 2 ActiveMQ brokers 5.5.0 with failover on Windows. I have a C#
windows service which connects to the broker queue via NMS. Windows service
creates 100 threads and each thread has its own consumer. I use
AutoAcknowledge mode. I run 4 instances of the windows service on separate
machines.
Your best bet is to try and create a test case that can reproduce the
issue. The stack traces look fine, seems they are waiting on more
messages.
Make sure you are using the latest NMS ActiveMQ version to ensure you
have all the latest fixes.
On Tue, 2012-02-07 at 05:17 -0800, Ishitori wrote:
It is hard to reproduce this problem in a test case.
But I do use latest version of ActiveMQ.NMS. I am also think about upgrading
5.5.0 ActiveMQ to 5.6.0 to resolve the problem with Scheduler (I use it for
redelivery).
Can you recommend me anything to get closer to the root of the problem?
--
