Mailing-List: contact dev-help@clerezza.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@clerezza.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
MIME-Version: 1.0
In-Reply-To: 
 <CALvhUEVWWgLK9vT9jUtnb4LfpgCfkmV4FZ5uhZDobCkOX=tbuA@mail.gmail.com>
References: 
 <CALvhUEUr=2nT9Uix4-9z8vqc595UsJ9uJNnnVoZ2mChAvabdWw@mail.gmail.com>
	<5271077E.5090506@xup.nl>
	<CALvhUEVWWgLK9vT9jUtnb4LfpgCfkmV4FZ5uhZDobCkOX=tbuA@mail.gmail.com>
Date: Tue, 3 Dec 2013 16:13:38 +0100
Message-ID: 
 <CALvhUEXgWbo56U2X2oC1ifp8e3ufpibXVPaGbyHmtKiX8kkX8A@mail.gmail.com>
Subject: Re: Problem with SingleTdbDatasetProvider
From: =?ISO-8859-1?Q?Reto_Bachmann=2DGm=FCr?= <reto@wymiwyg.com>
To: dev@clerezza.apache.org
Content-Type: multipart/alternative; boundary=001a11c33f7eb1dcb804eca2bd80

--001a11c33f7eb1dcb804eca2bd80
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So here's some code to reproduced the ConcurrentModificationException
directly with jena (using transactions):

        String directory =3D "target/Dataset1";
        Dataset dataset =3D TDBFactory.createDataset(directory);
        {
            dataset.begin(ReadWrite.WRITE);
            Model foo1 =3D ModelFactory.createDefaultModel();
            foo1.add(RDFS.Class, RDF.type, RDFS.Class);
            foo1.add(RDFS.Class, RDF.type, RDFS.Resource);
            dataset.addNamedModel(URNXFOO1, foo1);
            dataset.commit();
            dataset.end();
        }
        {
            dataset.begin(ReadWrite.WRITE);
            Model foo2 =3D ModelFactory.createDefaultModel();
            dataset.addNamedModel(URNXFOO2, foo2);
            dataset.commit();
            dataset.end();
        }
        {
            dataset.begin(ReadWrite.WRITE);
            Model foo1 =3D dataset.getNamedModel(URNXFOO1);
            Model foo2 =3D dataset.getNamedModel(URNXFOO2);
            StmtIterator iter =3D foo1.listStatements();
            while (iter.hasNext()) {
                foo2.add(iter.nextStatement());
            }
            dataset.commit();
            dataset.end();
        }


On Wed, Oct 30, 2013 at 2:42 PM, Reto Bachmann-Gm=FCr <reto@wymiwyg.com>wro=
te:

> Hi Minto
>
> Interesting problem you have there.
>>
>
> Thanks ;)
>
>>
>> Best is to fix the dreaded ConcurrentModificationException. Occasionally
>> I run into it it als well. But most probably it is not that trivial to
>> solve.
>>
>
> On hand we had some concurrency issues that caused the exception. I fixed
> (some of) them recently, the tests are now passing.
>
> On the other hand the exception is coming from Jena (as well as as from
> java collections) if the dataset (respectively the collection) is modifie=
d
> while iterating over it. Inthe case of addAll the modification of the
> underlying dataset is necessary, so this is not about some
> timing/concurrency.
>
> Cheers,
> Reto
>
>
>
>
>>
>> The only work around that I see is copy the MGraph to a different
>> provider and do the normal addAll(). This other provider does not
>> necessarily need to be in memory. Basically it is 2x addAll(). One to a
>> different provider and one back.
>>
>> My knowledge is too limited to comment on forwarding it to Jena.
>>
>> Hope this is of some help to you.
>>
>> Regards,
>>
>> Minto
>>
>> Reto Bachmann-Gm=FCr schreef op 30-10-2013 12:46:
>> > Hi
>> >
>> > I'm having a problem using addAll two add one Mgraph from
>> > SingeTdbDatasetProvider to another such MGraph.
>> >
>> > The problem is that the iterator over that added graph will return a
>> > ConcurrentModificationException as soon as a triple has been added to
>> the
>> > target graph.
>> >
>> > I don't know how to solve this. Copying the graph to be added to memor=
y
>> > doesn't seem to be a compealing solution. Maybe the add-all could be
>> > forwarded to Jena but this would solve the problem only in some cases,
>> not
>> > if there is any wrapper on the added graph or if union-graphs are used=
.
>> >
>> > Cheers,
>> > Reto
>> >
>>
>>
>> --
>> ir. ing. Minto van der Sluis
>> Software innovator / renovator
>> Xup BV
>>
>> Mobiel: +31 (0) 626 014541
>>
>>
>

--001a11c33f7eb1dcb804eca2bd80--