Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

ConcurrentModificationException from BaseEventTrackingService

Description

I'm seeing the following ConcurrentModificationException traceback in the logs for many different Sakai operations, though the error appears to be benign, it does fill up the logs. A couple ways to reproduce include modifying permissions in Resources or Matrix tool, or updating an assignment (but presumably any log-able event is causing this).

java.util.ConcurrentModificationException
at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449)
at java.util.AbstractList$Itr.next(AbstractList.java:420)
at org.sakaiproject.memory.impl.MultiRefCacheImpl.continueUpdate(MultiRefCacheImpl.java:295)
at org.sakaiproject.memory.impl.MultiRefCacheImpl.update(MultiRefCacheImpl.java:271)
at java.util.Observable.notifyObservers(Observable.java:142)
at org.sakaiproject.event.impl.BaseEventTrackingService.notifyObservers(BaseEventTrackingService.java:105)
.
.
.

Activity

Filter Maintainer August 8, 2008 at 6:03 AM

2.5.0 QA has been completed. Unfortunately, there were not resources available to specifically test this issue. If you find this to still be a problem in the latest release (at this point 2.5.2), please reopen the JIRA and add the latest affects version.

Megan May November 26, 2007 at 12:28 PM

Updating Fix version to 2.5.0_beta

Megan May November 19, 2007 at 12:07 PM

Merged into 2.5.x

Beth Kirschner November 16, 2007 at 11:44 AM

No sign of the crash slightly smiling face

Ian Boston November 16, 2007 at 10:50 AM

Beth,
I think I have fixed locally, can you check that you don't see the problem any more, and then assign to the 2.4.x maintanence role
Ian

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Created November 5, 2007 at 2:31 PM
Updated October 23, 2008 at 6:30 AM
Resolved November 16, 2007 at 10:50 AM

Flag notifications