Re: Fuseki service vs. webapp

2018-04-26 Thread Andy Seaborne
If the client software is not closing connections properly (and due to streaming, Content-Length isn't set so the client must call "close"), then there is a build-up of open sockets. This is especially true if the client and server are on the same machine. Even then, it is possible to over

Re: Fuseki service vs. webapp

2018-04-26 Thread Jean-Marc Vanel
Hi Sorin, you might want to try semantic_forms, another SPARQL server based on Jena TDB. This one is developed in Scala, on top of PlayFramework, itself on top of Netty 4.0.41.Final . Semantic_forms is also a generic semantic web navigation and annotation application, and a framework to build

Re: Fuseki service vs. webapp

2018-04-26 Thread Rob Vesse
Sorin Thanks for the report, unfortunately the lack of reproducible detail means I can only speculate on the source of the issues. The Jena project has only recently added a template service file for Fuseki so presumably when you say you are setting it up as a service either you define your

Fuseki service vs. webapp

2018-04-26 Thread Sorin Gheorghiu
Hi, Let's suppose Fuseki 3.6.0 is started as a service (and specific plugins like reindex, percolator, mustache, netty3 & 4 are loaded). Then a script which reads intensively data over SPARQL fails after the first ~400 SELECT's with connection refused error (Net::HTTP::Persistent::Error). It