Rahul Sharma created JENA-248:
---------------------------------
Summary: Fuseki server unresponsive when running multiple
construct queries using multi-threading.
Key: JENA-248
URL: https://issues.apache.org/jira/browse/JENA-248
Project: Apache Jena
Issue Type: Bug
Components: Fuseki
Affects Versions: Fuseki 0.2.1
Environment: Windows 7 (x64)
Reporter: Rahul Sharma
Hi Andy,
We are running concurrency tests for Fuseki 0.2.1 (downloaded from
http://www.apache.org/dist/incubator/jena/jena-fuseki-0.2.1-incubating/).
We're running multiple construct queries (approximately 200 queries) using Task
Parallel Library of .Net to talk to Fuseki and get response back. We've first
tried through dotNetRdf and when about 25 queries have run, the fuseki server
freezes and becomes unresponsive. To make it responsive again, we had to
restart the fuseki service.
Now the construct query is a bit that stands out here because its querying two
separate service endpoints. Following is the sample construct query that we're
using:
CONSTRUCT
{
<http://rahul.org/company/id/123456> ?predicate ?object .
?blankNode ?blankNodePredicate ?blankNodeObject .
<http://rahul.org/company/id/123456> ?pred ?blankNode1 .
?blankNode1 ?blankNodePredicate1 ?blankNodeObject1 .
}
WHERE
{
SERVICE <http://localhost:3030/companies/sparql>
{
<http://rahul.org/company/id/123456> ?predicate ?object .
}
SERVICE <http://localhost:3030/rahul/sparql>
{
OPTIONAL
{
<http://rahul.org/company/id/123456> ?pred ?blankNode1 .
?blankNode1 ?blankNodePredicate1 ?blankNodeObject1 .
}
}
}
Then we ran the queries again to make sure its not because of dotNetRdf - so
we've used a simple HttpWebRequest - something like this:
var request = HttpWebRequest.Create("http://localhost:3030/query/sparql?query="
+ GetUtf8(sparql)) as HttpWebRequest;
request.Method = "GET";
var response = request.GetResponse();
Could you please help with this problem of Fuseki server becoming unresponsive
in the above mentioned case.
Thanks,
Rahul
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira