No I am collecting any statements during the iterator into a temp model (or actually in some cases into a string that I read into a temp model and then .add to the InfModel. The CME occurs during simply iterating.
I went ahead and re-wrote the code with the com.hp.hpl.jena.util.iterator.ExtendedIterator<Triple> from the Graph.find method. It does seem to work, but is a bit more detailed (since it's dealing with Triples instead of Statements. What's the design thinking behind this restriction? On Fri, Sep 23, 2011 at 3:38 PM, Ignazio Palmisano < [email protected]> wrote: > On 23 September 2011 20:22, Erik Antelman <[email protected]> wrote: > > Okay, so I have a GenericRuleReasoner instance with a hybrid > configuration. > > I do some SPARQLCONSTRUCT on that InfModel and then add the results back > > into the InfModel. > > Everything looks like it works fine. > > > > Then I wanted to iterate over the model and compute something new > assertions > > myself. Being a newbie I used > > That's likely the issue. Are you adding new statements while > iterating? That's likely modifying the structures you're iterating > over, which is a lileky cause for CME. > HTH, > I. > > > StmtIterator sceneIter = sourceModel.listStatements(select); > > > > -- > > for(;;); /* [email protected] */ > > > -- for(;;); /* [email protected] */
