[
https://issues.apache.org/jira/browse/AMQ-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4224.
-----------------------------
Resolution: Fixed
consumer now gets notification of real effective prefetch so it can do a pull
when appropriate
> Setting queue policy queuePrefetch=0 in broker configuration causes messages
> to stay in pending state in broker - the messages aren't consumed
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-4224
> URL: https://issues.apache.org/jira/browse/AMQ-4224
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
> Affects Versions: 5.7.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Minor
> Labels: configuration, jms, prefetch, prefetch_size, pull
> Fix For: 5.8.0
>
>
> Broker prefetch config {code}<policyEntry queue="XX" ...
> queuePrefetch="0">{code} takes effect if the consumerInfo contains the
> default value (1000), indicating that it does not have a preference.
> However in the case that the broker chooses 0, to make all consumers pull
> messages, this information needs to be propagated back to the consumer to
> allow the receive(..) call to initiate a pull. Currently it is conditional on
> the consumer prefetch value == 0 which is currently not updated.
> The fix is to have the broker send a connection control message to update the
> prefetch when broker config uses 0, and have the receive(..) call check the
> current prefetch value.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
