Atomikos Forum

Spring DefaultMessageListenerContainer + Atomikos -> Memory Leak

I've tried the spring container like mentioned in the docs:

  <bean id="jmsContainer"
    <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" />

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.
Torsten Krah Send private email
Wednesday, March 24, 2010

If you can reproduce this then please send a zipped tm.out in DEBUG mode to our support email address. However, just 5 sessions is enough - no need to send 1OOO or more ;-)

Guy Pardon Send private email
Wednesday, March 24, 2010
This seems not to be an atomikos issue but a ActiveMQ one:
Torsten Krah Send private email
Wednesday, March 31, 2010

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics