Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <608713647.1245307087398.JavaMail.jira@brutus>
Date: Wed, 17 Jun 2009 23:38:07 -0700 (PDT)
From: "Joerg Schaible (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (COLLECTIONS-330) ConcurrentModificationException
 using remove from the keySet the LRUMap
In-Reply-To: <767941555.1245232447526.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COLLECTIONS-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721091#action_12721091 ] 

Joerg Schaible commented on COLLECTIONS-330:
--------------------------------------------

Thanks for heads-up. I "fixed" the invalid test, but it fails for me still. You did recognize that you have to rename the two tests with the TODO comment to get them running as unit test?

> ConcurrentModificationException using remove from the keySet the LRUMap
> -----------------------------------------------------------------------
>
>                 Key: COLLECTIONS-330
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-330
>             Project: Commons Collections
>          Issue Type: Bug
>          Components: Collection
>    Affects Versions: 3.3
>            Reporter: Joerg Schaible
>
> Even if the access to a LRUMap is synced and the remove method of the iterator is used that has been returned from the keySet of the LRUMap, it is possible to get a ConcurrentModificationException. This does not happen for remove of the iterators returned by the entrySet or values of the LRUMap. See currently not executed unit test in TestLRUMap (marked as TODO for COLLECTION-3).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.