Details
Description
Reported by Silvio Bierman on the jetty lists:
Hello all,
I got the CME in 6.1.5 this time:
Exception in thread "Timer-13" java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
at java.util.HashMap$KeyIterator.next(Unknown Source)
at
org.mortbay.jetty.servlet.AbstractSessionManager$Session.doInvalidate(AbstractSessionManager.java:954)
at
org.mortbay.jetty.servlet.AbstractSessionManager$Session.timeout(AbstractSessionManager.java:924)
at
org.mortbay.jetty.servlet.HashSessionManager.scavenge(HashSessionManager.java:200)
at
org.mortbay.jetty.servlet.HashSessionManager.access$000(HashSessionManager.java:36)
at
org.mortbay.jetty.servlet.HashSessionManager$1.run(HashSessionManager.java:144)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Jan Bartel [ janb ] | Greg Wilkins [ gregw ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 6.1.6rc1 [ 13653 ] | |
| Resolution | Fixed [ 1 ] |
I think this could only have happened if you had attribute listeners that modified other attributes?
I have refactored this method so this should be OK now, but I did not have a test case, so if you could test this
manually, that would be great.