[AMQ-3314] FilePendingMessageCursor isFull reports full in error when temp store is full, even if not needing the temp store

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.6.0
• Component/s: Broker
• Labels: block cursor memory temp topic usage
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 10/May/11 17:11
• Updated: 09/Apr/15 21:34
• Resolved: 10/May/11 17:17

Description

With slow queue consumers of non persistent messages the temp store can be filled and producers blocked. The default cursor for non persistent is a fileCursor.
However topic subs with a pending message limit strategy also use a cursor for pending messages. If there is sufficient memory resources, the topic consumers should be able to operate without recourse to the temp store. At the moment this is not the case, as the check to isFull reports true in error (based on the status of the temp store)
It should only report full if its memory is exhausted || it is spooling to disk AND the temp store is exhausted.

Issue Links

• is related to: AMQ-5716 TopicSubscription gets into endless loop when memory limit reached