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:48:57 UTC

[jira] Updated: (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:all-tabpanel ]

Arthur Naseef updated AMQ-3167:
-------------------------------

    Attachment: AMQ3167Test.java

Test use case which reproduces the problem consistently by using a small memory limit and short time delay between production and consumption.

A license header as been included; feel free to replace it as-needed.

> 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