activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: Camel consumers with prefetch set to 0
Date Fri, 18 Jan 2013 15:30:18 GMT
Hi Marco,

any chance you can create a test case that can reproduce the problem?

Also, can you share your connection settings? Some connection pooling
should help in your scenario.


Regards
--
Dejan Bosanac
----------------------
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosanac@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/


On Thu, Jan 17, 2013 at 9:50 AM, Marco.Crivellaro <marco.crive@gmail.com> wrote:
> the connection string provided was not valid, camel could not connect.
>
> we are currently using following connection string:
>
> failover:(tcp://hostname:61616?wireFormat.maxInactivityDuration=0&closeAsync=false)?jms.prefetchPolicy.queuePrefetch=0&initialReconnectDelay=10&maxReconnectDelay=15000
>
>
> we still see the same side effect of additional consumers:
>
> ID:hostname1-54045-1358405476533-1:1
>
> ID:hostname1-54045-1358405476533-1:2
>
> the first consumer does not have any dequeues and reports only one Enqueue.
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Camel-consumers-with-prefetch-set-to-0-tp4661702p4661860.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message