Hi everyone!Unfortunately, my first message here is about a problem.I have the following scenario: In an application, ActiveMQ (v5.13.1) is used as a communication channel between a large number of nodes (around 50). One queue is central, and through it all messages pass, they get process by 2 nodes, and then forwarded to other queues. Results of processing of those messages are then again sent back to the central queue. All messages are persistent as well.All nodes use Spring JMS to receive and send messages to all queues. The DefaultMessageListenerContainer in them are configured with concurrency ~ 50.All the queues have roughly the equal number of consumers. The central queue has most throughput (a few 100K of messages per day). Only 2 nodes (roughly 100 threads, i.e. 100 sessions) are consuming from it, and sending messages to it, and in addition to that all the other nodes send messages from it (at a lower rate though).For some time already, we see consumption rate from the central queue halting almost completely. There are messages in the queue, but our nodes are not getting any of those. When looked into JVM stacks, most were these:and these:Also, it happened that ActiveMQ restarted itself. From some answers from internet, a possible reason can be that AMQ's JVM was hanging, so the "starter" process had to restart it.I would imagine that the client code needs to be configured, however, there are 2 consumer nodes of this central queue, and BOTH are waiting for messages, excluding any kind of mutual locking, and possibly indicating an issue with how ActiveMQ and/or KahaDB handle this situation.Any kind of advise as to how to solve this problem is appreciated!Thanks,Haris
-- View this message in context: http://activemq.2283324.n4.nabble.com/Consumers-hanging-on-a-queue-although-there-are-messages-in-it-tp4707719.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
