Tadayoshi Sato created AMQ-6603:

             Summary: Excessive number of consumers when used with 
PooledConnectionFactory and Failover transport
                 Key: AMQ-6603
                 URL: https://issues.apache.org/jira/browse/AMQ-6603
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client
    Affects Versions: 5.14.3
            Reporter: Tadayoshi Sato

When {{PooledConnectionFactory}} is used with Failover transport, insufficient 
access control settings on the broker result in an excessive number of consumer 
objects on the broker once the access control settings are properly set. 

Here is an example Spring XML configuration:

<beans ...>

  <bean id="jmsConnectionFactory" 
    <property name="brokerURL" value="failover:(tcp://localhost:61616)" />
    <property name="userName" value="test" />
    <property name="password" value="test" />

  <bean id="pooledConnectionFactory" 
    <property name="connectionFactory" ref="jmsConnectionFactory" />
    <property name="maxConnections" value="10" />

  <bean id="jmsContainer" 
    <property name="connectionFactory" ref="pooledConnectionFactory" />
    <property name="destinationName" value="TEST" />
    <property name="messageListener" ref="messageListener" />
    <property name="concurrentConsumers" value="10" />

  <bean id="messageListener" class="com.redhat.issues.amq.SpringJmsConsumer" />


In this configuration we expect only one connection and 10 consumers for 
{{TEST}} queue, but after following the reproducer steps we see around 100 
consumers for the queue on hawtio.

This message was sent by Atlassian JIRA

Reply via email to