[
https://issues.apache.org/jira/browse/ARTEMIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-289:
-----------------------------------
Description:
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.
(was: 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.)
> 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)
