I'm wondering if its a XA problem, or look into adjusting your pool
config. It currently allows a max of 500 connections. For consuming,
4-5 max connections per CPU core is usually a good ratio.
On 2/14/12 10:12 AM, john wrote:
I think I'm only using spring for transactions. Here's the configuration I
have:
<bean name="activemq"
class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="transacted" value="true" />
<property name="transactionManager" ref="jmsTxManager" />
<property name="connectionFactory" ref="pooledConnectionFactory" />
</bean>
<bean id="PROPAGATION_REQUIRED"
class="org.apache.camel.spring.spi.SpringTransactionPolicy">
<property name="transactionManager" ref="jmsTxManager"/>
<property name="propagationBehaviorName"
value="PROPAGATION_REQUIRED"/>
</bean>
<bean id="PROPAGATION_REQUIRES_NEW"
class="org.apache.camel.spring.spi.SpringTransactionPolicy">
<property name="transactionManager" ref="jmsTxManager"/>
<property name="propagationBehaviorName"
value="PROPAGATION_REQUIRES_NEW"/>
</bean>
<bean name="jmsTxManager"
class="org.springframework.jms.connection.JmsTransactionManager">
<property name="connectionFactory" ref="pooledConnectionFactory" />
</bean>
<bean id="pooledConnectionFactory"
class="org.apache.activemq.pool.PooledConnectionFactory">
<property name="maxConnections" value="8" />
<property name="maximumActive" value="500" />
<property name="connectionFactory" ref="activeMqConnectionFactory"
/>
</bean>
<bean id="activeMqConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="${amq.brokerURL}" />
</bean>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQConnection-leak-tp4387316p4387524.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
