clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <>
Subject [jira] [Commented] (CLEREZZA-745) ConcurrentModicationException on TDB storage provider (SingleDataset)
Date Wed, 10 Jul 2013 15:45:55 GMT


Reto Bachmann-Gmür commented on CLEREZZA-745:

I'm occasionally getting this error on running the tests, not sure if related:
java.util.ConcurrentModificationException: Iterator: started at 99459, now 99460
	at com.hp.hpl.jena.tdb.sys.DatasetControlMRSW.policyError(
	at com.hp.hpl.jena.tdb.sys.DatasetControlMRSW.access$000(
	at com.hp.hpl.jena.tdb.sys.DatasetControlMRSW$IteratorCheckNotConcurrent.checkCourrentModification(
	at com.hp.hpl.jena.tdb.sys.DatasetControlMRSW$
	at org.apache.jena.atlas.iterator.Iter.count(
	at com.hp.hpl.jena.graph.impl.GraphBase.size(
	at org.apache.clerezza.rdf.core.impl.util.PrivilegedTripleCollectionWrapper$
	at org.apache.clerezza.rdf.core.impl.util.PrivilegedTripleCollectionWrapper$
	at Method)
	at org.apache.clerezza.rdf.core.impl.util.PrivilegedTripleCollectionWrapper.size(
	at org.apache.clerezza.rdf.core.access.LockableMGraphWrapper.size(

> ConcurrentModicationException on TDB storage provider (SingleDataset)
> ---------------------------------------------------------------------
>                 Key: CLEREZZA-745
>                 URL:
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Rupert Westenthaler
> As reported by Minto van der Sluis in [1] the SingleDataset Jena TDB TcProvider can throw
.ConcurrentModificationException when iterating over a read protected MGraph and a modification
is done to an other graph managed in the same Jena TDB Dataset. This includes creating a new
graph in the dataset.
> Based on a first analysis this is caused by the Single Dataset Jena TDB TcProvider using
per TripleCollections ReadWrite Locks instead of a single ReadWrite Lock for all graphs managed
by the same Jena TDB Dataset.
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message