On 27/08/13 19:25, Rob Vesse wrote:
But If I
stop the JVM of my Fuseki server (and TDB) from my IDE console, restart
it
and then query the dataset, the query returns to me null values for some
elements of some triples.
How do you stop the JVM? Also what is your TDB setup?
This sounds like one of two things:
1 - Dataset corruption possibly caused by non-graceful shutdown of the
server, once the dataset is corrupted you typically need to start afresh.
2 - Your TDB dataset is not persistent (are you using the --memTDB option?)
Usually dataset corruption would be indicated by error messages in the
logs so if you didn't see those I would lean more towards it being option 2
Rob
Why can't you upgrade? Fuseki is a standalone. I hope you are not
accessing the database from TDB directly at the same time that Fuseki is
running. That will corrupt the data.
Andy
On 8/27/13 11:08 AM, "Davide Rossi" <[email protected]> wrote:
Hi everyone,
I'm using Fuseki 0.2.4 with TDB 0.9.3 (I know that are old version, but
unfortunately I can't change to another version). The problem is the
seguent: I write triples using Fuseki, than I query the dataset (using
Fuseku, of course) and the query returns all values correctly. But If I
stop the JVM of my Fuseki server (and TDB) from my IDE console, restart it
and then query the dataset, the query returns to me null values for some
elements of some triples.
My question is: is this a bug of TDB or Fuseki version I'm using (I thinks
TDB can't persist all inserted data) and than solved in new versions ? If
is not, can I do something to solve it?
Thanks a lot
Regards
Davide
