You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2015/10/29 21:32:27 UTC

[jira] [Resolved] (ARTEMIS-289) Potential ConcurrentModificationException when closing connections

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

Justin Bertram resolved ARTEMIS-289.
------------------------------------
    Resolution: Fixed

> Potential ConcurrentModificationException when closing connections
> ------------------------------------------------------------------
>
>                 Key: ARTEMIS-289
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-289
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>             Fix For: 1.1.1
>
>
> org.apache.activemq.artemis.core.server.impl.QueueImpl#getConsumers returns the actual Set of consumers, but if another thread modifies this collection while the caller loops through the Set then a ConcurrentModificationException will be thrown.  This is possible particularly in management operations that work on the Set of consumers like org.apache.activemq.artemis.api.core.management.ActiveMQServerControl#closeConsumerConnectionsForAddress.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)