Apache Artemis-Apache骆驼线程消费者随着时间的推移变得缓慢

Question

我正在运行ApacheArtemis Broker 2.14.0。以下是用户连接配置：

<beans
   xmlns="http://www.springframework.org/schema/beans"
   xmlns:aop="http://www.springframework.org/schema/aop"
   xmlns:context="http://www.springframework.org/schema/context"
   xmlns:jee="http://www.springframework.org/schema/jee"
   xmlns:tx="http://www.springframework.org/schema/tx"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://www.springframework.org/schema/aop 
      http://www.springframework.org/schema/aop/spring-aop-3.1.xsd
      http://www.springframework.org/schema/beans
      http://www.springframework.org/schema/beans/spring-beans-3.1.xsd
      http://www.springframework.org/schema/context
      http://www.springframework.org/schema/context/spring-context-3.1.xsd
      http://www.springframework.org/schema/jee
      http://www.springframework.org/schema/jee/spring-jee-3.1.xsd
      http://www.springframework.org/schema/tx
      http://www.springframework.org/schema/tx/spring-tx-3.1.xsd
      http://camel.apache.org/schema/spring
      http://camel.apache.org/schema/spring/camel-spring.xsd">
      
   <bean class="com.test.CustomProcessBean" id="CustomProcessBean" scope="prototype"/>
   
   <bean id="jmsCF" class="org.apache.qpid.jms.JmsConnectionFactory">
      <property name="remoteURI"  value="ampq://myhost:5672"/>
   </bean>
   
   <bean id="jmsPooledCF" class="org.messaginghub.pooled.jms.JmsPoolConnectionFactory" init-method="start" destroy-method="stop">
      <property name="maxConnections" value="3" />
      <property name="connectionFactory" ref="jmsCF" />
   </bean>
   
   <bean id="jmsConfig" class="org.apache.camel.component.jms.JmsConfiguration">
      <property name="connectionFactory" ref="jmsPooledCF" />
      <property name="concurrentConsumers" value="5" />
      <property name="maxConcurrentConsumers" value="10" />
   </bean>
   
   <bean id="jms" class="org.apache.camel.component.amqp.AMQPComponent">
      <property name="configuration" ref="jmsConfig" />
      <property name="transacted" value="true" />
   </bean>
   
   <bean id="errHandler" class="org.apache.camel.builder.DeadLetterChannelBuilder">
      <property name="deadLetterUri" value="jms:queue:customDLQ"/>
      <property name="redeliveryPolicy" ref="customRedeliveryPolicyConfig"/>
   </bean>
   
   <bean id="customRedeliveryPolicyConfig" class="org.apache.camel.processor.RedeliveryPolicy">
      <property name="maximumRedeliveries" value="3"/>
      <property name="redeliveryDelay" value="8000"/>
   </bean>
   
   <camelContext id="camel"
      xmlns="http://camel.apache.org/schema/spring">
      <endpoint id="etams" uri="jms:queue:test-queue" />
      <route errorHandlerRef="errHandler" >
         <from uri="ref:etams"/>
         <convertBodyTo type="java.lang.String" />
         <threads id="threadedprocess" maxQueueSize="5" poolSize="5" maxPoolSize="5" customId="true" >
            <bean ref="CustomProcessBean" method="processMessage"/>
         </threads>
      </route>
   </camelContext>
   
</beans>

首先，该路由每秒处理约100条消息。随着时间的推移（约6小时），它下降到每秒约25条消息。

在Artemis web控制台的“Consumers”选项卡中，我注意到每个会话都是关闭的，并且经常创建。

从经纪人方面，我们已经提供了足够的12G内存。代理在启用持久性的情况下运行，传入消息大小小于5kb。

驼峰线程是否会随着时间的推移尝试创建更多会话？这是反模式吗？这是消费者超时处理消息的原因吗？当我在配置中不使用Camel线程时（即只使用




Answer 1

我也遇到了同样的问题，通过将JMSendpoint中的cacheLevelName选项设置为CACHE\u CONSUMER解决了这个问题。通过启用事务处理选项，最终将缓存级别设置为cache_NONE。

本节将更好地解释：JMS组件-事务和缓存级别