incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Vesse (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-179) On Linux Fuseki will create user owned temporary files that block other users from using the full Fuseki Web UI
Date Fri, 16 Dec 2011 21:46:30 GMT


Rob Vesse commented on JENA-179:

Hi Paolo

We run Fuseki via code because we have a lot of custom query engine code to communicate with
our backend databases.

We can have multiple databases running on a single machine and we have 1:1 relationship between
Fuseki instances and database instances.  Each Fuseki instance is running on a different port

This is primarily done so that databases can be managed and brought up and down entirely separately
from each other.  But there are other architectural/technical reasons which I can't disclose
which require that this arrangement has to be in place.

In production this will probably become a non-issue as all Fuseki-database pairs will likely
be brought up and down by a single user and in most scenarios there will only actually be
one pair.  But currently the developers are running into issues because we're all running
separate instances as we work on testing different parts of our product.

> On Linux Fuseki will create user owned temporary files that block other users from using
the full Fuseki Web UI
> ---------------------------------------------------------------------------------------------------------------
>                 Key: JENA-179
>                 URL:
>             Project: Jena
>          Issue Type: Bug
>          Components: Fuseki
>         Environment: SUSE Linux 11
>            Reporter: Rob Vesse
> Fuseki seems to create temporary files under Linux which are owned by the running user
and blocks any other users from running Fuseki properly because servlets will not function
> Going to the control panel will produce the following trace:
> Error 500: /tmp/org/apache/jsp/ (Permission denied)
> /tmp/org/apache/jsp/ (Permission
> 	at Method)
> 	at<init>(
> 	at<init>(
> 	at org.apache.jasper.compiler.JDTJavaCompiler.getJavaWriter(
> 	at org.apache.jasper.compiler.Compiler.generateJava(
> 	at org.apache.jasper.compiler.Compiler.compile(
> 	at org.apache.jasper.JspCompilationContext.compile(
> 	at org.apache.jasper.servlet.JspServletWrapper.service(
> 	at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> 	at org.apache.jasper.servlet.JspServlet.service(
> 	at javax.servlet.http.HttpServlet.service(
> 	at org.eclipse.jetty.servlet.ServletHolder.handle(
> 	at org.eclipse.jetty.servlet.ServletHandler.doHandle(
> 	at org.eclipse.jetty.server.session.SessionHandler.doHandle(
> 	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
> 	at org.eclipse.jetty.servlet.ServletHandler.doScope(
> 	at org.eclipse.jetty.server.session.SessionHandler.doScope(
> 	at org.eclipse.jetty.server.handler.ContextHandler.doScope(
> 	at org.eclipse.jetty.server.handler.ScopedHandler.handle(
> 	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
> 	at org.eclipse.jetty.server.Server.handle(
> 	at org.eclipse.jetty.server.HttpConnection.handleRequest(
> 	at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(
> 	at org.eclipse.jetty.http.HttpParser.parseNext(
> 	at org.eclipse.jetty.http.HttpParser.parseAvailable(
> 	at org.eclipse.jetty.server.HttpConnection.handle(
> 	at org.eclipse.jetty.server.nio.BlockingChannelConnector$
> 	at org.eclipse.jetty.util.thread.QueuedThreadPool$
> 	at
> Fuseki - version 0.2.0 (Date: 2011-12-15T15:19:16-0800)
> It looks like these temporary files are being generated by one of the components Fuseki
relies upon rather than Fuseki itself but this is an issue for us because if one user has
run Fuseki another user may be completely blocked from using the web based UI fully.
> Interestingly servlets will still function correctly, e.g. I can still issue queries
directly to /dataset/query and get a response but the lack of a control panel is inconvenient.
> This may not be fixable due to it actually being caused by a component that Fuseki depends
upon but I have no expertise in Jetty/JSP/Servlets so I don't know against what project this
bug should actually be filed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message