Re: Forward/backward rules (and reasoner memory leaks)

Hi Martynas, On 20/06/16 22:18, Martynas Jusevičius wrote: Hey, after using GenericRuleReasoner and InfModel more extensively, we started experiencing memory leaks that eventually kill our webapp because it runs out of heap space. Jena version is 2.11.0. After some profiling, it seems that RET

Re: Forward/backward rules (and reasoner memory leaks)

We have outstanding: https://github.com/apache/jena/pull/47 which changes the cache to LRU from fixed. That does not fix any memory leaks but might mitigate them. There are two FIXME in the PR which could do with looking at. Andy On 21/06/16 09:28, Dave Reynolds wrote: Hi Martynas, On 2

Re: Riot CMD: parsing invalid data returns exit code 0

On 20/06/16 22:06, Jindřich Mynarz wrote: On Mon, Jun 20, 2016 at 10:39 PM, Andy Seaborne wrote: Shell magic are be applied: capture the output and test it. If in a subshell, the exit here will set the out $? - #!/bin/bash ( X="$(riot --validate ... 2&>1)" if [[ -n "$X"

Re: Riot CMD: parsing invalid data returns exit code 0

On 21/06/16 10:16, Andy Seaborne wrote: An exit code would be good - a contribution maybe? Recorded as: https://issues.apache.org/jira/browse/JENA-1197

Re: Upgrade to Jena 3.1.0 breaks the query

Alex, Thanks - the key point here is TDB - it follows a slightly different path through the code. https://issues.apache.org/jira/browse/JENA-1198 The best workaround for Fuseki I came up with is to add a context setting to the dataset: :tdb_dataset_readwrite a tdb:DatasetTD

Re: Upgrade to Jena 3.1.0 breaks the query

Thank, Andy. The workaround fixed the problem in my environment. Alex On 21.06.16 14:01, Andy Seaborne wrote: Alex, Thanks - the key point here is TDB - it follows a slightly different path through the code. https://issues.apache.org/jira/browse/JENA-1198 The best workaround for Fuseki I c

Re: Upgrade to Jena 3.1.0 breaks the query

On 21/06/16 12:07, Alex Shkop wrote: Thank, Andy. The workaround fixed the problem in my environment. Good to know that. The next snapshot dev build should have a proper fix. Andy Alex On 21.06.16 14:01, Andy Seaborne wrote: Alex, Thanks - the key point here is TDB - it follows

got exception on specific query

Hi, I got exception when calling QueryFactory.create(query); where query is following: PREFIX v: PREFIX rdf: SELECT (COUNT(?idObj) AS ?idCount) WHERE { { SELECT ?person ?idObj WHERE { ?person v:hasUniqueID ?idObj .

Re: got exception on specific query

What puzzling me more, the code currently being deployed actually never passed that second arg, but it doesn't throw exception. The Jena API version is same, I made some changes at other places, but not on that particular code. This is so weird.. From: Zen 980

Re: got exception on specific query

Which version are you using? > com.hp.hpl.jena. Jena2, not Jena3. Andy On 21/06/16 16:11, Zen 98052 wrote: What puzzling me more, the code currently being deployed actually never passed that second arg, but it doesn't throw exception. The Jena API version is same, I made some chang

Re: got exception on specific query

Yes, still using Jena 2, to be precise, v2.13.0 From: Andy Seaborne Sent: Tuesday, June 21, 2016 3:19:17 PM To: users@jena.apache.org Subject: Re: got exception on specific query Which version are you using? > com.hp.hpl.jena. Jena2, not Jena3. Andy

Re: Forward/backward rules (and reasoner memory leaks)

What about https://issues.apache.org/jira/browse/JENA-650? On Tue, Jun 21, 2016 at 10:59 AM, Andy Seaborne wrote: > We have outstanding: > > https://github.com/apache/jena/pull/47 > > which changes the cache to LRU from fixed. > That does not fix any memory leaks but might mitigate them. > > Ther

Re: got exception on specific query

On 21/06/16 21:02, Zen 98052 wrote: Yes, still using Jena 2, to be precise, v2.13.0 I tried the query in various versions (3.x, 2.13.0, 2.11) and they all work. My test was to run "qparse" on the query which calls QueryFactory.parse Andy From: An

Re: got exception on specific query

Yes, that's really weird. It works fine on previous deployment (using same version of Jena, and same call to QueryFactory.create) Do you see any problem if I pass Syntax.syntaxARQ? Thanks, Z From: Andy Seaborne Sent: Tuesday, June 21, 2016 4:55:28 PM To: use

Re: got exception on specific query

On 21/06/16 22:09, Zen 98052 wrote: Yes, that's really weird. It works fine on previous deployment (using same version of Jena, and same call to QueryFactory.create) Do you see any problem if I pass Syntax.syntaxARQ? Yes - the underlying fault is still there! The exception message is as far

Re: got exception on specific query

Thanks Andy! Aside from this bizarre issue, i'd think passing syntaxARQ is fine, because it's an extension of syntaxSPARQL_11, right? From: Andy Seaborne Sent: Tuesday, June 21, 2016 6:00:29 PM To: users@jena.apache.org Subject: Re: got exception on specific que