You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Arthur Naseef (JIRA)" <ji...@apache.org> on 2011/02/09 17:53:57 UTC

[jira] Commented: (AMQ-3167) possible skipped Queue messages in memory limited configuration with fast consumers

    [ https://issues.apache.org/jira/browse/AMQ-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992569#comment-12992569 ] 

Arthur Naseef commented on AMQ-3167:
------------------------------------

In the process of creating a bug report for the test case attached above, this bug report appeared to capture the problem.  Trying to backport this fix to 5.4.2, there appears to be a number of changes on which this patch depends.  Any guidance on a shorter workaround until we can upgrade to 5.5 would be appreciated.

The test case attached represents a use pattern we need to support, but has been narrowed down to detect a lost message in the timeframe it takes to trigger this issue.

> 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
>
>
> 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