Are you saying that you update the data in the underlying TDB dataset directly? I.e. not via Fuseki
If so please don't do this, this is highly likely to lead to database corruption since TDB is designed such that only one JVM manages the dataset at any one time. Rob On 09/12/2013 11:24, "Arto My Friend" <[email protected]> wrote: > Hi there Jena and Fuseki folks, > >I have problem about Fuseki not reloading updated data from update via TDB >api. > >My jena-fuseki version is 1.0.0 > >./fuseki-server --update --loc=MY_DB_FOLDER /xxx > >I use TDB API version 1.0.0 >and apapche-jena-libs 2.11.0 + all dependency hooked via maven > >The update sometimes show when refresh URL at > >http://localhost:3030/xxx/query?query=SELECT+*+%7B+%3Fs+%3Fp+%3Fo+%7D&outp >ut=text&stylesheet= > >Sometimes, the update will appear as corrupted table while most of the >time >there will be no change at all. > >Only after restart fuseki server then the update will be shown correctly. > >Is this normal behavior? Or does the real-time update only possible by >SPARQL Update query through it's REST api? > >Note: >There is no message in terminal saying that fuseki is running in update >enabled mode when starting the server, when though I already pass in the >option via command line. > >20:15:03 INFO Server :: TDB dataset: >directory=MY_DB_FOLDER/ > >20:15:04 INFO Config :: Home Directory: >/Users/Noname/dev/jena-fuseki-1.0.0 > >20:15:04 INFO Server :: Dataset path = /xxx > >20:15:04 INFO Server :: Fuseki 1.0.0 >2013-09-12T10:49:49+0100 > >20:15:04 INFO Server :: Started 2013/12/09 20:15:04 JST on >port 3030
