[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[jira] [Commented] (ARIES-1837) ConcurrentModificationException in InterestManager.endpointChanged

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

ASF subversion and git services commented on ARIES-1837:

Commit 39dde12bf51b7a702d298f4033efbb98e119b9e8 in aries-rsa's branch refs/heads/master from [~chris@xxxxxxxxxxxxxxxxx]
[ https://gitbox.apache.org/repos/asf?p=aries-rsa.git;h=39dde12 ]

ARIES-1837 - Avoid ConcurrentModificationException by using ConcurrentHashmap and remove ineffective synchronized

> ConcurrentModificationException in InterestManager.endpointChanged
> ------------------------------------------------------------------
>                 Key: ARIES-1837
>                 URL: https://issues.apache.org/jira/browse/ARIES-1837
>             Project: Aries
>          Issue Type: Bug
>          Components: Remote Service Admin
>    Affects Versions: rsa-1.12.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>            Priority: Major
>             Fix For: rsa-1.13.0
> In InterestManager.endpointChanged we iterate through the interests in an unsafe way:
>         *for* (Interest interest : interests.values())
> As interests is a simple HashMap this fails if an endpoint is added or removed while iterating.
> I propose to use a ConcurrentHashMap instead to fix this.

This message was sent by Atlassian JIRA