Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 vhle01@gmail.com does not designate 162.253.133.43 as permitted sender)
Date: Thu, 29 Jan 2015 15:12:36 -0800 (PST)
From: vhle01 <vhle01@gmail.com>
To: dev@activemq.apache.org
Message-ID: <1422573156651-4690688.post@n4.nabble.com>
Subject: Why does the AdvisoryConsumer only ACK messages once it reaches 75%
 of prefetch?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

While running through some test, I noticed that the AdvisoryConsumer, which
is created automatically if you have watchTopicAdvisories enabled, is only
acknowledging message once it reaches 75% of prefetch. Is there any
particular reason for that? It just seems a little strange. On the broker, I
can see that the messages are being delivered but not acknowledged.

Can someone provide a good explanation for this? Or is this a minor bug?

Here's a link to the class...lines 68-78:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-client/src/main/java/org/apache/activemq/AdvisoryConsumer.java;h=1e65ffb06b7ff1c01f3405dde1a84def9a0b4aa1;hb=refs/heads/trunk


--
View this message in context: http://activemq.2283324.n4.nabble.com/Why-does-the-AdvisoryConsumer-only-ACK-messages-once-it-reaches-75-of-prefetch-tp4690688.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.