-
Bug
-
Resolution: Done
-
Major
-
6.0.2.Final
-
None
From Dennis Reed:
A ConcurrentModificationException in the CacheWriter interceptor during a commit.
java.util.ConcurrentModificationException
at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:953)
at java.util.LinkedList$ListItr.next(LinkedList.java:886)
at org.infinispan.interceptors.CacheWriterInterceptor.store(CacheWriterInterceptor.java:210)
at org.infinispan.interceptors.CacheWriterInterceptor.commitCommand(CacheWriterInterceptor.java:115)
The code is looping through the modifications associated with the transaction:
List<WriteCommand> modifications = ctx.getCacheTransaction().getAllModifications();
...
210: for (WriteCommand cacheCommand : modifications) {
The transaction's modification list is stored as a synchronized list with a comment "we need to synchronize this collection to be able to get a valid snapshot from another thread during state transfer".
But this thread is not doing state transfer, and I'd assume "get a valid snapshot" wouldn't include modification?
Is it valid for this list to be modified from another thread (in which case all iterations should be synchronized), or is something modifying it incorrectly?
[ISPN-5379] Persistence with stringKeyedJdbcStore throwing ConcurrentModificationException while adding data to cache
Dave Stahl <dstahl@redhat.com> changed the Status of bug 1212505 from MODIFIED to ON_QA
Sebastian Łaskawiec <slaskawi@redhat.com> changed the Status of bug 1212505 from POST to MODIFIED
Will Burns
added a comment - dberinde@redhat.com posted https://github.com/infinispan/infinispan/pull/3625#issuecomment-128294561 In that case we might as well just close this and wait for another bug report 
Will Burns
added a comment - dberinde@redhat.com posted https://github.com/infinispan/infinispan/pull/3625#issuecomment-128294561 In that case we might as well just close this and wait for another bug report Dan Berindei <dberinde@redhat.com> changed the Status of bug 1212505 from ASSIGNED to POST
Will Burns
added a comment - Reopening, however https://github.com/infinispan/infinispan/pull/3625 has been integrated. That PR doesn't fix the issue however and is to help highlight the actual issue when it occurs again.
If desired this could be closed and another logged at a later point for the issue when reproduced.
Will Burns
added a comment - Reopening, however https://github.com/infinispan/infinispan/pull/3625 has been integrated. That PR doesn't fix the issue however and is to help highlight the actual issue when it occurs again.
If desired this could be closed and another logged at a later point for the issue when reproduced. Dan Berindei <dberinde@redhat.com> changed the Status of bug 1212505 from NEW to ASSIGNED
Martin Gencur <mgencur@redhat.com> changed the Status of bug 1212505 from ON_QA to VERIFIED