[
https://issues.apache.org/jira/browse/CASSANDRA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842835#action_12842835
]
Jonathan Ellis commented on CASSANDRA-757:
------------------------------------------
were you able to reproduce before, and not w/ this patch? because AFAIK using
an iterator manually instead of a foreach only helps when the CME is from
modifying the collection in the same loop, and you can replace that w/
iter.remove(). otherwise if the CME is happening from another thread modifying
stuff you have to move to a Concurrent collection.
> FatClient removal causes ConcurrentModificationException
> --------------------------------------------------------
>
> Key: CASSANDRA-757
> URL: https://issues.apache.org/jira/browse/CASSANDRA-757
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.5
> Environment: debian lenny amd64 OpenJDK 64-Bit Server VM (build
> 1.6.0_0-b11, mixed mode)
> Reporter: Brandon Williams
> Assignee: Jaakko Laine
> Priority: Minor
> Fix For: 0.7
>
> Attachments: 757.txt
>
>
> After using a fatclient and killing it, I later receive this ST on all nodes:
> INFO 16:04:58,999 FatClient /10.242.4.13 has been silent for 3600000ms,
> removing from gossip
> ERROR 16:04:58,999 Fatal exception in thread Thread[Timer-1,5,main]
> java.lang.RuntimeException: java.util.ConcurrentModificationException
> at
> org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:96)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> Caused by: java.util.ConcurrentModificationException
> at java.util.Hashtable$Enumerator.next(Hashtable.java:1048)
> at org.apache.cassandra.gms.Gossiper.doStatusCheck(Gossiper.java:382)
> at
> org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:90)
> ... 2 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
