On 12/08/2016 07:24 AM, Patrick Vansevenant wrote:
Great idea ! But I don't experience any improvement with a
usePrefetchExtension set to "false".
I don't know of the broker destination policy settings in general work
together with an AMQP client ?
--
View this message in context:
Great idea ! But I don't experience any improvement with a
usePrefetchExtension set to "false".
I don't know of the broker destination policy settings in general work
together with an AMQP client ?
--
View this message in context:
What about setting the usePrefetchExtension policy to "false"?
Then the broker will wait for the consumer to acknowledge that the message
is processed before refilling the prefetch buffer.
tabish...@gmail.com wrote
> On 12/07/2016 05:09 PM, Patrick Vansevenant wrote:
>> I have opened JIRA
On 12/07/2016 05:09 PM, Patrick Vansevenant wrote:
I have opened JIRA https://issues.apache.org/jira/browse/AMQ-6530.
I will certainly try ActiveMQ 5.14.2 at the moment it is released !
--
View this message in context:
I have opened JIRA https://issues.apache.org/jira/browse/AMQ-6530.
I will certainly try ActiveMQ 5.14.2 at the moment it is released !
--
View this message in context:
On 12/06/2016 03:58 PM, Patrick Vansevenant wrote:
Your explanation is very valuable and completely correct in my opinion.
Nevertheless there are some differences concerning the queuePrefetch between
version 5.14.1 and 5.13.3.
The Dispatched Queue contains maximum one message in 5.13.3 with a
Your explanation is very valuable and completely correct in my opinion.
Nevertheless there are some differences concerning the queuePrefetch between
version 5.14.1 and 5.13.3.
The Dispatched Queue contains maximum one message in 5.13.3 with a
queuePrefetch of one and that at any point in time.
Sounds like it is working as intended if I understand the usage you are
saying is happening. The client will refill the link credit in this
case every time a message is either read via (receive, receiver(timed)
or receiveNoWait) or when a message is handed off to an async consumer.
This
I'm talking about queues with a low message volume and high processing time.
In such a setup is it important that messages are not "heaping up" in the
dispatch queue.
The queueprefetch must be one in order to keep it workable.
I have done some tests with an ActiveMQ 5.14.1 broker and an AMQP
