To wrap this up, Dave, you are right about a resource being found that
was not an OntClass. Most select rows were as expected, but it did find
a solution where the resource had an additional rdf:type that was not an
owl:Class. Problem solved, thanks for the help everyone.
On 11/1/2021 1:27 P
On 01/11/2021 17:18, Steve Vestal wrote:
Thanks, this started me down the path to a solution.
For the record, I searched through my code, and I could not find
multiple threads accessing the model. This was occurring during a
SPARQL query of an OntModel. Is it possible ARQ uses threads? Below
Thanks, this started me down the path to a solution.
For the record, I searched through my code, and I could not find
multiple threads accessing the model. This was occurring during a
SPARQL query of an OntModel. Is it possible ARQ uses threads? Below is
what I tried, which it seems does add
Steve,
Is your usage multithreaded? If so, you'll need to make sure that usage
is mutlireaer or single writer.
Using jena transaction mecahnism is best - they work with datasets and
choose the best implementation for the datasets. For ones containing
inference, that's MRSW locking.
Anoth
Does anyone have any suggestions on things to try to avoid a
ConcurrentModificationException when using
OWLReasoner.OWL_MEM_MICRO_RULE_INF? Or what the potential consequences
of that are? (The below stack dump only goes back to where my code made
the call, the full one is fairly lengthy and f
