n,
There is work-in-progress to improve configuration : JENA-1731.
This includes setting context on endpoint and dataset as well as
server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have just had a problem with query timeout overrides when
upgrading to Fuseki 3.12.0. I think the issu
I've just spotted something in the documentation that means this
discussion is going to get a little more complicated.
I will therefore start a separate thread.
Brian
On 31/08/2019 22:40, Chris Tomlinson wrote:
Hi Brian,
The Lucene version changed in 3.10.0 to 7.4 from 6.4 in 3.9.0 (and ear
: JENA-1731.
This includes setting context on endpoint and dataset as well as
server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have just had a problem with query timeout overrides when
upgrading to Fuseki 3.12.0. I think the issue is related to
JENA-1620 [1] which was deployed with
Hi Chris,
Thank you for responding.
On 31/08/2019 22:40, Chris Tomlinson wrote:
Hi Brian,
The Lucene version changed in 3.10.0 to 7.4 from 6.4 in 3.9.0 (and earlier). I
don’t think this has anything to do with the problem though.
I’m surprised that the query you indicate works in 3.9.0. It l
Hi Brian,
The Lucene version changed in 3.10.0 to 7.4 from 6.4 in 3.9.0 (and earlier). I
don’t think this has anything to do with the problem though.
I’m surprised that the query you indicate works in 3.9.0. It looks like what’s
intended is a phrase query but it needs to be surrounded by double
it out when you get to
that point.
Brian
On 05/08/2019 17:56, Andy Seaborne wrote:
Hi Brian,
There is work-in-progress to improve configuration : JENA-1731.
This includes setting context on endpoint and dataset as well as
server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have
out when you get to
that point.
Brian
On 05/08/2019 17:56, Andy Seaborne wrote:
Hi Brian,
There is work-in-progress to improve configuration : JENA-1731.
This includes setting context on endpoint and dataset as well as
server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have jus
> > I see, thanks for the answer! There seem be some way to have a timeout
> > in the Lucene API, but it doesn't look very straightforward... should
> > I open a separate issue to track that?
>
> Yes
Ok, I'll do that
> Are you able to contribute for this additional feature?
Perhaps in the future
On 30/08/2019 11:57, Élie Roux wrote:
Hi all,
It is "graceful termination" - the query engine checks whether the
timeout has gone off, not have something interrupt a thread.
Looking at the code, the Lucene call is returning an array of ScoreDocs
in one go so that is going to all happen.
Th
Hi all,
> It is "graceful termination" - the query engine checks whether the
> timeout has gone off, not have something interrupt a thread.
>
> Looking at the code, the Lucene call is returning an array of ScoreDocs
> in one go so that is going to all happen.
>
> The rest of the query processing w
On 29/08/2019 08:53, Élie Roux wrote:
Dear All,
We actually have a very similar plan:
- an endpoint for general queries, with a shortish timeout
- an endpoint for admin queries, with a much longer one, using the same dataset
The first thing I wanted to know is if and how Fuseki can be asked
i Brian,
There is work-in-progress to improve configuration : JENA-1731. This
includes setting context on endpoint and dataset as well as server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have just had a problem with query timeout overrides when
upgrading to Fuseki 3.12.0. I thin
rian
On 05/08/2019 17:56, Andy Seaborne wrote:
Hi Brian,
There is work-in-progress to improve configuration : JENA-1731. This
includes setting context on endpoint and dataset as well as server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have just had a problem with query ti
Dear All,
We actually have a very similar plan:
- an endpoint for general queries, with a shortish timeout
- an endpoint for admin queries, with a much longer one, using the same dataset
The first thing I wanted to know is if and how Fuseki can be asked to
completely stop a query thread (the quer
Brian
On 05/08/2019 17:56, Andy Seaborne wrote:
Hi Brian,
There is work-in-progress to improve configuration : JENA-1731. This
includes setting context on endpoint and dataset as well as server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have just had a problem with query ti
erver.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have just had a problem with query timeout overrides when upgrading
to Fuseki 3.12.0. I think the issue is related to JENA-1620 [1]
which was deployed with Jena 3.10.0.
Essentially, JENA-1620 modified the query timeout override
function
Hi Brian,
There is work-in-progress to improve configuration : JENA-1731. This
includes setting context on endpoint and dataset as well as server.
Andy
On 05/08/2019 13:57, Brian McBride wrote:
I have just had a problem with query timeout overrides when upgrading to
Fuseki 3.12.0. I
I have just had a problem with query timeout overrides when upgrading to
Fuseki 3.12.0. I think the issue is related to JENA-1620 [1] which was
deployed with Jena 3.10.0.
Essentially, JENA-1620 modified the query timeout override functionality
to constrain timeout overrides so that they must
.
@prefix ja:<http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix text:<http://jena.apache.org/text#> .
@prefix skos:<http://www.w3.org/2004/02/skos/core#>
@prefix fuseki:<http://jena.apache.org/fuseki#> .
On 10/06/2019 14:46, Marco Neumann wrote:
did you set the ja: na
a.hpl.hp.com/2008/tdb#> .
@prefix ja:<http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix text:<http://jena.apache.org/text#> .
@prefix skos:<http://www.w3.org/2004/02/skos/core#>
@prefix fuseki:<http://jena.apache.org/fuseki#> .
On 10/06/2019 14:46, Marco Ne
pload "upload" ; # Non-SPARQL
> >> upload service
> >> fuseki:serviceReadWriteGraphStore "data" ; # SPARQL Graph
> >> store protocol (read and write)
> >> fuseki:dataset :text_dataset ;
> >>
com/2005/11/Assembler#> .
@prefix text:<http://jena.apache.org/text#> .
@prefix skos:<http://www.w3.org/2004/02/skos/core#>
@prefix fuseki:<http://jena.apache.org/fuseki#> .
On 10/06/2019 14:46, Marco Neumann wrote:
did you set the ja: name space?
On Mon, Jun 10, 2019 at 11
3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#> .
@prefix tdb:<http://jena.hpl.hp.com/2008/tdb#> .
@prefix ja:<http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix text:<http://jena.apache.org/text#> .
@prefix skos:<h
le/#> .
@prefix rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#> .
@prefix tdb:<http://jena.hpl.hp.com/2008/tdb#> .
@prefix ja:<http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix text:<http://jena.apache.org/
onfig:
> >>
> >> @prefix :<http://localhost/jena_example/#> .
> >> @prefix rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
> >> @prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#> .
> >> @prefix tdb:<http://jena.hpl.hp.
9/02/22-rdf-syntax-ns#> .
@prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#> .
@prefix tdb:<http://jena.hpl.hp.com/2008/tdb#> .
@prefix ja:<http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix text:<http://jena.apache.org/text#> .
@prefix skos:<htt
efix tdb:<http://jena.hpl.hp.com/2008/tdb#> .
@prefix ja:<http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix text:<http://jena.apache.org/text#> .
@prefix skos:<http://www.w3.org/2004/02/skos/core#>
@prefix fuseki:<http://jena.apache.org/fuseki#> .
On 1
>
> @prefix fuseki:<http://jena.apache.org/fuseki#> .
>
>
> On 10/06/2019 14:46, Marco Neumann wrote:
> > did you set the ja: name space?
> >
> > On Mon, Jun 10, 2019 at 11:04 AM Mikael Pesonen <
> mikael.peso...@lingsoft.fi>
> > wrote:
&
at 11:04 AM Mikael Pesonen
wrote:
How do you set query timeout? I've tried on config.ttl
[] rdf:type fuseki:Server ;
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "3000" ] ;
and
:my_dataset rdf:type tdb:DatasetTDB ;
ja:context [ ja:
did you set the ja: name space?
On Mon, Jun 10, 2019 at 11:04 AM Mikael Pesonen
wrote:
>
> How do you set query timeout? I've tried on config.ttl
>
> [] rdf:type fuseki:Server ;
> ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "3000&qu
How do you set query timeout? I've tried on config.ttl
[] rdf:type fuseki:Server ;
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "3000" ] ;
and
:my_dataset rdf:type tdb:DatasetTDB ;
ja:context [ ja:cxtName "arq:queryTimeout"
Rajiv,
I have failed to reproduce this. I ran a Fuseki server and sent 1000's
of ASK queries to it. No threads were created.
I used quite simple ASK queries - maybe there is complexity in queryStr?
The results of an ASK query are about 400 bytes on the wire, including
HTTP header - that fi
t OS will still be ack'ing the TCP connection and may do so
forever from a server-style app like from Tomcat.
Setting the query time may reduce the general effect but it will not free
up threads. A query timeout is a graceful abort of the query - the query
gets a chance to clean up and th
nnelConnector but it is possible to complete take control of
>>> the
>>> jetty configuration with --jetty-config.
>>>
>>> (SelectChannelConnector might have been better but it has been reported
>>> to
>>> be unstable on OS/X for Fuseki's
tyle app like from Tomcat.
Setting the query time may reduce the general effect but it will not free
up threads. A query timeout is a graceful abort of the query - the query
gets a chance to clean up and that needs the query execution in the server
getting called.
Actually killing threads in
om/blogs/securitylabs/2011/11/02/
> how-to-protect-against-slow-http-attacks
>
> The client OS will still be ack'ing the TCP connection and may do so
> forever from a server-style app like from Tomcat.
>
> Setting the query time may reduce the general effect but it will not f
umption side, not the request sending.
https://community.qualys.com/blogs/securitylabs/2011/11/02/how-to-protect-against-slow-http-attacks
The client OS will still be ack'ing the TCP connection and may do so
forever from a server-style app like from Tomcat.
Setting the query time may reduce the genera
Hi Rajiv,
You can find how to set query timeouts in the Fuseki documentation at [1]
To set server wide timeout:
[] rdf:type fuseki:Server ;
#Server-wide context parameters can be given here.
#For example, to set query timeouts: on a server-wide basis:
#Format 1: "10
Hi,
Our application which is running at Tomcat server is making query to Fuseki
TDB store using HTTP protocol.
We have observed that thread count for the Fuseki process is increasing
with time.
I know there might be code issue and resources should be closed properly.
*But we would like to achie
39 matches
Mail list logo
