Hi
I guess the config changes are after you set cacheConsumers=false. And
you use the spring connection pool.
Well for what it is worth you cannot cache consumers when doing
request/reply and when JMSCorrelationIDs is in-use, such as you do.
As a new consumer must be created before a new JMSSelector can be
re-created with any new messages to pickup. If the consumer is cached
then no new consumer is created, and then no new JMSSelector is
created (will just re-use the old one), and then no new messsages is
picked up.
You can configure the replyToCacheLevelName option for fine grained control.
You can configure this in the endpoint uri directly also
?replyToCacheLevelName=CACHE_NONE
On Mon, Nov 5, 2012 at 3:51 PM, anaCortes <anquiroe...@hotmail.com> wrote:
> Hi,
>
>> What version of Camel are you using?
> 2.10.2
>
>> And how have you configured the JMS component
>
> <bean id="activemq"
> class="org.apache.activemq.camel.component.ActiveMQComponent">
> <property name="configuration" ref="amqConfigNoTransaction"/>
> </bean>
>
> <bean id="amqConfigNoTransaction" parent="amqCommonConfig"
> class="org.apache.camel.component.jms.JmsConfiguration">
> <property name="transacted" value="false"/>
> </bean>
>
> <bean id="amqCommonConfig" abstract="true"
> class="org.apache.camel.component.jms.JmsConfiguration">
> <property name="connectionFactory" ref="cachedConnectionFactory"/>
> <property name="concurrentConsumers" value="1"/>
> <property name="exceptionListener" ref="jmsExceptionListener"/>
> </bean>
>
> <bean id="cachedConnectionFactory"
> class="org.springframework.jms.connection.CachingConnectionFactory">
> <property name="targetConnectionFactory" ref="connectionFactory"/>
> <property name="sessionCacheSize" value="100"/>
> <property name="cacheConsumers" value="false" />
> </bean>
>
> <bean id="connectionFactory"
> class="org.apache.activemq.ActiveMQConnectionFactory">
> <property name="brokerURL" value="${activemq.brokerURL}"/>
> <property name="userName" value="${activemq.username}"/>
> <property name="password" value="${activemq.password}"/>
> <property name="exceptionListener" ref="jmsExceptionListener"/>
> <property name="transportListener" ref="jmsTransportListener"/>
> <property name="redeliveryPolicy" ref="redeliveryPolicy"/>
> </bean>
>
> ...
>
>> and the route where you do request/reply?
>
> .to(ExchangePattern.InOut,
> "activemq:ActiveMQ.DLQ?replyTo=xxx.REPLY&requestTimeout=255000&receiveTimeout=250&timeToLive=510000")
>
> How could this cacheConsumer="false" affect to the performance?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/JMS-Shared-fixed-reply-queue-doesn-t-consume-all-the-messages-tp5721700p5722155.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
