[
https://issues.apache.org/jira/browse/AMQ-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arthur Naseef updated AMQ-3167:
-------------------------------
Attachment: patch.amq3167.activemq-5.4.2
Patch against 5.4.2 that resolves this issue, created from a subset of the
changes made on the trunk for this bug report.
> possible skipped Queue messages in memory limited configuration with fast
> consumers
> -----------------------------------------------------------------------------------
>
> Key: AMQ-3167
> URL: https://issues.apache.org/jira/browse/AMQ-3167
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
> Attachments: AMQ3167Test.java, patch.amq3167.activemq-5.4.2
>
>
> regression in test from https://issues.apache.org/jira/browse/AMQ-2413
> required some investigation. Symptom was missing messages, turned out to be
> in the middle of the sequence. Issue with the priority kahadb cursors and
> setbatch. Set batch is invoked when the cursor memory is exhausted such that
> replay from the store can start at the correct point. If a call to setBatch
> was followed by a call to recover when there was still no memory space
> available, the cursor could skip the next pending message.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
