activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Created) (JIRA)" <>
Subject [jira] [Created] (AMQ-3700) java.util.ConcurrentModificationException in
Date Mon, 06 Feb 2012 16:49:59 GMT
java.util.ConcurrentModificationException in

                 Key: AMQ-3700
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.5.1
            Reporter: Timothy Bish
            Assignee: Timothy Bish
            Priority: Minor
             Fix For: 5.6.0

The following stack was reproduced in AMQ 5.5.1 but not the Fuse Message Broker version.


Exception in thread "BrokerService[3561F026-E8F62746-2A202922-F17EADF0-7BCA8E67] Task-5053"
jvm 1    | 	at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(
jvm 1    | 	at java.util.LinkedHashMap$
jvm 1    | 	at
jvm 1    | 	at org.apache.activemq.thread.PooledTaskRunner.runTask(
jvm 1    | 	at org.apache.activemq.thread.PooledTaskRunner$
jvm 1    | 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
jvm 1    | 	at java.util.concurrent.ThreadPoolExecutor$
jvm 1    | 	at


This can happened only in the case where the optimizedDispatch mode is enabled and multiple
producers are waiting for space.  When the memory usage decreases and the notifications are
run from the iterate() method the method can be called recursively leading to the error as
items are removed from the messagesWaitingForSpace map.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message