activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian D. Johnson" <br...@thejohnsonfamily.name>
Subject Re: Why does the AdvisoryConsumer only ACK messages once it reaches 75% of prefetch?
Date Tue, 03 Feb 2015 14:37:50 GMT
The default topic prefetch in ActiveMQPrefetchPolicy is 32767, which means
the broker is keeping around references to at least ~24500 messages per
client before the client's first ACK.  Unless there is an extremely high
volume of temporary destinations being created, this 75% limit seems to be
set arbitrarily high based on ActiveMQ's default configuration.  I second
the request to revisit this.  At a minimum, the 75% threshold should be
reduced to something more reasonable.  Ideally, the ActiveMQ client would
auto-ACK Advisory messages or provide a configuration option (for clients
experiencing performance issues) to ACK these messages in reasonable batch
sizes.


On Thu, Jan 29, 2015 at 7:07 PM, artnaseef <art@artnaseef.com> wrote:

> It is intentional to improve performance.  Sending an ack for every message
> increases overhead.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Why-does-the-AdvisoryConsumer-only-ACK-messages-once-it-reaches-75-of-prefetch-tp4690688p4690690.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message