Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-1072
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Timothy Bish
Reporter: Dave Stanley
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

java.util.ConcurrentModificationException in org.apache.activemq.broker.region.Queue.iterate()

Created: 31/Jan/12 04:49 PM   Updated: 06/Feb/12 09:46 PM
Component/s: broker
Affects Version/s: None
Fix Version/s: 5.5.0-fuse-00-xx, 5.6.0-fuse-00-00, 5.5.1-fuse-02-02

Environment: 5.5.1 AMQ

External Issue URL: https://issues.apache.org/jira/browse/AMQ-3700


 Description  « Hide
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" java.util.ConcurrentModificationException
jvm 1    | 	at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:373)
jvm 1    | 	at java.util.LinkedHashMap$ValueIterator.next(LinkedHashMap.java:388)
jvm 1    | 	at org.apache.activemq.broker.region.Queue.iterate(Queue.java:1376)
jvm 1    | 	at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:127)
jvm 1    | 	at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)
jvm 1    | 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
jvm 1    | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
jvm 1    | 	at java.lang.Thread.run(Thread.java:662)

This issue is to audit the pagedInMessages LinkedHashMap and verify its protected sufficiently.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Timothy Bish added a comment - 06/Feb/12 09:46 PM
Fix applied.