consumer.receive(poll timeout in milli)
On 15 November 2013 16:28, Ned Wolpert wrote:
> With prefetch=0, the client polls the server then, right? Is polling
> frequency a settable value? (Though as I write this, I'm assuming if so,
> it would be set on the client-side.)
>
>
> On Fri, Nov 15, 201
With prefetch=0, the client polls the server then, right? Is polling
frequency a settable value? (Though as I write this, I'm assuming if so,
it would be set on the client-side.)
On Fri, Nov 15, 2013 at 4:55 AM, Gary Tully wrote:
> prefetch=0 will do it, so long as you don't use a messageliste
prefetch=0 will do it, so long as you don't use a messagelistener
directly. via spring the listener does a receive(...) under the hood
so it will be ok with prefetch=0
On 14 November 2013 16:14, Ned Wolpert wrote:
> After I say you wrote 'prefetchExtension=false' I looked it up and found
> this b
After I say you wrote 'prefetchExtension=false' I looked it up and found
this bug sounds exactly like what I'm hitting:
https://issues.apache.org/jira/browse/AMQ-2651 which led me to you talking
on
http://grokbase.com/t/activemq/users/103bdh5cgx/prefetchextension-off-by-1-for-transacted-consumers-w
can you try a different ack mode, like clientack or using transactions
- the prefetch will be deferred till the ack which will be later than
in the auto ack case. Also, in the transacted case, use the
destination policy prefetchExtension=false
On 13 November 2013 14:54, Ned Wolpert wrote:
> Did a
Did anyone have an idea into what I could do different to route messages to
idle consumers? Just came into the same situation this morning where a
queue has 1 message processing on one consumer, one message waiting, and 15
idle consumers. (See notes below for my current configs)
On Wed, Nov 6,
Forgot to add, broker url only has one query param
jms.prefetchPolicy.queuePrefetch=1
which, as I mentioned above, does seem to work.
On Tue, Nov 5, 2013 at 10:56 AM, Ned Wolpert wrote:
> I can see the preFetch values being set in the console, and they are all
> one. I've not set prioritie
I can see the preFetch values being set in the console, and they are all
one. I've not set priorities.
These are 'java' processes, using groovy/grails. The same executable on 4
boxes, each executable with 4 listeners, treaded. Using the grails jms
plugin, which wraps the Spring jms template config
Have you verified via broker logging that the prefetch values you've
configured are being honored by the broker? Are consumer priorities in
use? Are your consumers instances of the same executable or are they
implemented individually?
Can you post your broker configuration: activemq.xml?
How are
Thanks for the response...
Any idea on the round-robin not working? I have a queue with 16 consumers,
all have pre-fetch set to 1. Five consumers are actively processing
requests and 3 requests are pending the 11 other consumers are idle.
History has shown that a new request may go to one of t
The clients should negotiate the correct open-wire (protocol version)
so in theory the broker will be backward compatible with older
clients. Just make sure the activemq-openwire-legacy jar is on the
classpath (should be by default).
Of course I would test this out to make sure :)
On Mon, Nov 4,
11 matches
Mail list logo
