Atomikos Forum |
|
I've tried the spring container like mentioned in the docs:
<bean id="jmsContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer"> <property name="connectionFactory" ref="jmsFactory" /> <property name="destination" ref="topic" /> <property name="messageListener" ref="indexService" /> <property name="transactionManager" ref="transactionManager" /> <property name="sessionTransacted" value="true" /> <property name="subscriptionDurable" value="true" /> <property name="durableSubscriptionName" value="indexJmsContainer" /> <property name="concurrentConsumers" value="1" /> </bean> If i do this my app does run into OOM after time. Looking at the heap dump, i've got too many ActiveMQXASession instances (>10000) which are hanging around vs. only 2 if i use the MessageDrivenContainer. So using Atomikos JMS Factory + Spring DefaultMessageListenerContainer is not possible because it does leak those Sessions. Is this a known problem? What can i do about it? I've got some sample app to show this problem. thx for help.
This seems not to be an atomikos issue but a ActiveMQ one:
https://issues.apache.org/activemq/browse/AMQ-2556 |