You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Seelmann (JIRA)" <ji...@apache.org> on 2009/10/07 16:00:31 UTC

[jira] Resolved: (DIRSTUDIO-532) Refreshing parent of referral may give ConcurrentModificationException

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

Stefan Seelmann resolved DIRSTUDIO-532.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0
         Assignee: Stefan Seelmann

This should be fixed with commit 775025. The listener map is cloned now before iterating through it.

> Refreshing parent of referral may give ConcurrentModificationException
> ----------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-532
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-532
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 1.4.0
>            Reporter: Martin Alderson
>            Assignee: Stefan Seelmann
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> When expanding a container that contains a referral for the first time the follow referral dialog is shown.  Selecting the same connection to handle the referral and then refreshing the container sometimes (usually within 10 attempts) shows a ConcurrentModificationException:
> Error while reading entry
>   java.util.ConcurrentModificationException
> 	at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
> 	at java.util.HashMap$KeyIterator.next(Unknown Source)
> 	at org.apache.directory.studio.ldapbrowser.core.events.EventRegistry.fireEntryUpdated(EventRegistry.java:348)
> 	at org.apache.directory.studio.ldapbrowser.core.jobs.InitializeAttributesRunnable.runNotification(InitializeAttributesRunnable.java:153)
> 	at org.apache.directory.studio.connection.core.jobs.StudioConnectionJob.run(StudioConnectionJob.java:119)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>   java.util.ConcurrentModificationException
> After acknowledging the error no other problems are noticeable.

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