Why ConcurrentConsumers not scaling down in activemq ?

Solution In Progress - Updated -

Environment

  • Red Hat JBoss A-MQ
    • 6.1.0

Issue

  • Why the maxConcurrentConsumers not scaling down?
  • Version: ActiveMQ 5.9.0.redhat-610379 is setup with the following:
max.consumers = 12
min.consumers = 4

Via Camel route it is configured as

maxConcurrentConsumers = 12
concurrentConsumers = 4
  • Following attribute is set in the spring config still it has no effect.
<property name="maxConcurrentConsumers" value="${max.consumers}" />
  • When the consumers are started 4 are displayed correctly via jmx and the web console. 100 messages are sent and the consumers scale up to 12 as expected. However, when there are zero messages left the consumer count never goes down. However this still displays 12 consumers when it should be four. Why is it still showing 12 connected?

Resolution

Jira was raised for the scenario: https://issues.jboss.org/browse/ENTMQ-976

Set the property maxMessagesPerTask at the consumer end .

refer: https://cwiki.apache.org/confluence/display/CAMEL/JMS

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.