Re: fuseki 3.5.0 upload error

same error in fuseki 3.5.0 Result: failed with message "SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data" It works fine in fuseki 3.4.0 2017-11-07 10:51 GMT-07:00 Andy Seaborne : > Recorded as JENA-1420 (it POSTs to the wrong URL) > > I've

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

so I did a quick test with a fresh build and it's recurring via https access requests on jetty. I think we can close this issue here in the AJF3.6.0 thread. On Fri, Nov 17, 2017 at 11:57 PM, Marco Neumann wrote: > did an update yesterday. I will dig into this over the

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

did an update yesterday. I will dig into this over the weekend. On Fri, Nov 17, 2017 at 6:53 PM, Andy Seaborne wrote: > > > On 17/11/17 15:59, Marco Neumann wrote: >> >> just switched to AJF3.6.0 (TDB) . It's the first time I see this. >> >> the index + spatial is older and was

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

On 17/11/17 15:59, Marco Neumann wrote: just switched to AJF3.6.0 (TDB) . It's the first time I see this. the index + spatial is older and was created with AJF3.4.0 (TDB) I will do an update and see if that makes a difference On Fri, Nov 17, 2017 at 4:53 PM, ajs6f

problem with query builder

Hi, I was experimenting with the query builder and hit a problem when I was attempting to construct an Expr. This example: package com.epimorphics.scratch; import org.apache.jena.arq.querybuilder.ConstructBuilder; import org.apache.jena.sparql.expr.E_GreaterThan; import

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

just switched to AJF3.6.0 (TDB) . It's the first time I see this. the index + spatial is older and was created with AJF3.4.0 (TDB) I will do an update and see if that makes a difference On Fri, Nov 17, 2017 at 4:53 PM, ajs6f wrote: > 0x3 is Ctrl-C. Does this happen

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

0x3 is Ctrl-C. Does this happen repeatedly? Can you cause it to happen? How is the request to Fuseki being generated? ajs6f > On Nov 17, 2017, at 10:48 AM, Marco Neumann wrote: > > this was (with some delay) followed by a >

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

this was (with some delay) followed by a ?query=ASK%0AWHERE%0A++%7B+%3Fs+%3Fp+%3Fo%7D%0A no activity otherwise [2017-11-17 10:28:36] Fuseki INFO [17] GET http://www.lotico.com:3030/lotico/sparql?query=ASK%0AWHERE%0A++%7B+%3Fs+%3Fp+%3Fo%7D%0A [2017-11-17 10:28:36] Fuseki INFO [17] GET

Re: HttpParser WARN Illegal character 0x3 in state AJF3.6.0

Can you provide some more context please? How did you cause this? What was the operation and the data? ajs6f > On Nov 17, 2017, at 10:36 AM, Marco Neumann wrote: > > does this looks familiar? > > HttpParser WARN Illegal character 0x3 in state=START for buffer >

HttpParser WARN Illegal character 0x3 in state AJF3.6.0

does this looks familiar? HttpParser WARN Illegal character 0x3 in state=START for buffer HeapByteBuffer@6a797a1b[p=1,l=47,c=8192,r=46]={\x03<<<\x00\x00/*\xE0\x00\x00\x00\x00\x00Cookie:...nistr\r\n\x01\x00\x08\x00\x03\x00\x00\x00>>>6

Re: HDT with Fuseki 3.4.0

Hi Domi, HDT depends on Jena 3.0.1 (8-Dec-2015). There will be other changes so fixing one class and using later version of Jena is not guaranteed to work. Surely, it's not just putting back one class - it's switching back to using that class as used by Jena's RDFDataset assembler etc etc.

HDT with Fuseki 3.4.0

Hi, I tried running HDT ( http://www.rdfhdt.org/manual-of-hdt-integration-with-jena/) on my fuseki 3.4.0 server. When doing a query, I get a NoClassDefFoundError for org.apache.jena.sparql.core.DatasetGraphMaker I saw that this class existed till v3.0.1 and got deleted in this commit

Re: TDB1/TDB2 disk space with and without named graphs

On 16/11/17 21:37, Andy Seaborne wrote: On 16/11/17 20:36, Osma Suominen wrote: Andy Seaborne kirjoitti 16.11.2017 klo 22:04: TDB1 or HDT. TDB2 has no benefits for you at 40M triples at occasional updates. Compaction would be a benefit, if it could be automated. But apparently not in