Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 31 Aug 2012 02:19:07 +1100 (NCT)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <1572362575.16820.1346339948035.JavaMail.jiratomcat@arcas>
In-Reply-To: <1827121548.30200.1345475978027.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (AMQ-3982) Overlapping PList iterators can read
 wrong data or throw exceptions about chunk streams not existing.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-3982:
----------------------------

    Attachment: new.txt

a variant of the concurrent add iterate test that fails
                
> Overlapping PList iterators can read wrong data or throw exceptions about chunk streams not existing.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3982
>                 URL: https://issues.apache.org/jira/browse/AMQ-3982
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Critical
>             Fix For: 5.7.0
>
>         Attachments: new.txt
>
>
> When multiple PList iterators are in use and happen have an overlapping read of PageFile data on disk they can reset each others seek offset and cause an exception to be thrown about "chunk stream does not exist" or read of a page in the Free list.  The reason is that the hasNext of PList iterator needs to by sync'd on the index lock to prevent two iterators from entering into a readPage call concurrently.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira