Hello,
after about 1 day usage, I got a strange situation - there are lot of
ActiveMQMessageConsumers created (~640k) with selector
JMSCorrelationID='CamelDummyJmsMessageSelector'. All consumer objects use
around 1GB heap memory.
Camel route is quite simple:
<route id="...">
<from ref="..." />
<setExchangePattern pattern="InOut" />
<.. removing some headers from exchange...>
<doTry>
<recipientList>
<method ref="queueMapper" method="mapSync" />
</recipientList>
<doCatch>....</doCatch>
</doTry>
</route>
queueMapper bean just returns String from properties, in this case it is
"activemq:REQUEST?replyTo=RESPONSE&receiveTimeout=250&requestTimeout=34000"
ActiveMQ configuration:
<osgi:reference id="jmsConnectionFactory"
interface="javax.jms.ConnectionFactory" filter="(name=activemq)" />
<bean id="jmsConfiguration"
class="org.apache.camel.component.jms.JmsConfiguration">
<property name="connectionFactory" ref="jmsConnectionFactory" />
<property name="transacted" value="false" />
<property name="maxConcurrentConsumers" value="5" />
<property name="cacheLevelName" value="CACHE_NONE" />
</bean>
<bean id="activemq"
class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="configuration" ref="jmsConfiguration" />
</bean>
Heap usage is growing, consumer objects are not cleaned and heap growing
dosn't depend on system load. But when doing a heap dump, most of consumers
are destoyed (in my case, ~700mb heap memory was released).
Any ideas why camel creates so many activemq consumers with
JMSCorrelationID='CamelDummyJmsMessageSelector'? As I understand, with such
correlationId no messages will be received ever....
camel version 2.7.1.fuse-00-43
java 1.6.0_43
Justas
--
View this message in context:
http://camel.465427.n5.nabble.com/Lots-of-ActiveMQMessageConsumer-with-selector-JMSCorrelationID-CamelDummyJmsMessageSelector-tp5736921.html
Sent from the Camel - Users mailing list archive at Nabble.com.
