Error 500: No known block type for 0

Discussion:

Abduladem Eljamel

2016-03-22 19:37:52 UTC

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

Andy Seaborne

2016-03-23 17:38:08 UTC

Permalink

Post by Abduladem Eljamel
Error 500: No known block type for 0
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

Abduladem Eljamel

2016-03-23 22:32:18 UTC

Permalink

Hi Andy
Thank you for answering my email.
Actually, I am using Jena transactionally with (begin-commit-end)

I noticed that the error realted to the graphs in the data store because whenI query the data targeting the default graph, there is no error even though with emptyresults.ThanksAbdulÂ Â
________________________________
From: Andy Seaborne <***@apache.org>
To: ***@jena.apache.org
Sent: Wednesday, 23 March 2016, 17:38
Subject: Re: Error 500: No known block type for 0

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

Abduladem Eljamel

2016-03-24 15:11:21 UTC

Permalink

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 <***@apache.org>
To: ***@jena.apache.org
Sent: Wednesday, 23 March 2016, 17:38
Subject: Re: Error 500: No known block type for 0

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

Andy Seaborne

2016-03-24 19:34:04 UTC

Permalink

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
Sent: Wednesday, 23 March 2016, 17:38
Subject: Re: Error 500: No known block type for 0

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