On 24/03/16 15:11, Abduladem Eljamel wrote:
Hi,,This email is to update the information in previous email related to this 
error:"Error 500: No known block type for 0" I found that the TDB data store is 
corrupted after I useFuseki server to query it?After loading the store to Fuseki server 
and query it, Igot the message above even when use Jena API to query. If I don't use 
Fuseki, Ican still query the store with any problems. I am using Fusekei 1.0.2 with 
default settings. Thiscommand I use:fuseki-server --loc=myTDBLocation /myName ThanksAbdul

       From: Andy Seaborne <[email protected]>
  To: [email protected]
  Sent: Wednesday, 23 March 2016, 17:38
  Subject: Re: Error 500: No known block type for 0

On 22/03/16 19:37, Abduladem Eljamel wrote:
Hi allI hope you are all fine.I have a TDB store contains a small data. When I 
query that data directly from JENA, I got results and it works fine. But when I 
use Fuseki server (1.0.2) to query the same data with the same SPARQL code, I 
got this error:
Error 500: No known block type for 0

The data contains two named graphs and the SPARQL query is:

SELECT * WHERE { GRAPH ?g { ?s ?p ?o}}

I would be very gratefull if any one tell me what is the cause of this error.

Thans in advance
Abdul


A possible cause is that you used non-transactionally in the past and
didn't flush changes to disk one time, or the app crashed.

The files on disk are in a bad state and you need to reload the data.

Fuseki always updates TDB transactionally if the service is acting
directly on TDB.  Direct use from Jena can be transactionally
(begine-commit-end) or non-transactionally.

     Andy

If the store is corrupted, it happened at sometime in the past. These are silent errors that cause the messages like you are seeing only at some later time.

I suggest you rebuild the database. Upgrading to the latest release (Fuseki 1.3.1 or Fuseki 2.3.1, Jena 3.0.1) would be a good idea.

If you can reproducibly cause this error from a clean server, we might be able to help but the information so far does not enable anyone to reproduce the situation.

        Andy


Reply via email to