[
https://issues.apache.org/jira/browse/AMQ-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-7240.
-----------------------------
Resolution: Invalid
This doesn't appear to be a bug but a normal consequence of using JMSTemplate
without a pooling solution: Refer to
https://activemq.apache.org/jmstemplate-gotchas
> Large Number of ActiveMQ Connection Executor Threads on client
> --------------------------------------------------------------
>
> Key: AMQ-7240
> URL: https://issues.apache.org/jira/browse/AMQ-7240
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.15.8
> Reporter: Sumit Bhardwaj
> Priority: Major
>
> We are using ActiveMQ version 5.15.8, We are connecting to it using Spring
> JMSTemplate. What we are seeing is in case of connection errors too many of
> following threads get created
>
> "ActiveMQ Connection Executor.."
>
> In one instance around 1250 Threads for the above were active in our tomcat
> hosting our web application, when maxConnections setting on activeMQ was
> 1000.
>
> The behaviour is similar to the following defect
> https://issues.apache.org/jira/browse/AMQ-6700
> which was fixed in 5.14.6, but we are seeing in 5.15.8 as well.
>
> Spring Version: 5.0.6.RELEASE
> ActiveMQ Version 5.1.5.8
>
> Spring Configuration
>
> <!-- Template class for sending messages. -->
> <bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate;">
> <constructor-arg ref="authenticationConnectionFactory"></constructor-arg>
> <property name="sessionTransacted" value="false"></property>
> <property name="deliveryPersistent" value="true"></property>
> <property name="defaultDestination" ref="jmsTemplateDest"></property>
> </bean>
>
> <!-- Beans for connection factory and destination queues -->
> <bean id="activemqConnectionFactory"
> class="org.apache.activemq.ActiveMQConnectionFactory">
> <property name="brokerURL" value="${activemq.broker.url}"></property>
> </bean>
>
> <bean id="jmsTemplateDest" class="org.apache.activemq.command.ActiveMQQueue">
> <constructor-arg index="0" value="${queue.name}"/>
> </bean>
>
> Is there any workaround for this bug? Or do we need to change any
> configuration?
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
