[AMQ-4224] Setting queue policy queuePrefetch=0 in broker configuration causes messages to stay in pending state in broker - the messages aren't consumed

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.7.0
• Fix Version/s: 5.8.0
• Component/s: Broker, JMS client
• Labels: configuration jms prefetch prefetch_size pull
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 14/Dec/12 15:49
• Updated: 02/May/13 02:29
• Resolved: 17/Dec/12 13:46

Description

Broker prefetch config

<policyEntry queue="XX" ... queuePrefetch="0">

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.

Issue Links

• is depended upon by: AMQ-4226 Broker destination zero prefetch and RAR endpoint listener are incompatible b/c RAR is starved of messages - log an error to highlight