incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (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 Mon, 19 Dec 2011 14:07:30 GMT


Andy Seaborne commented on JENA-179:

I agree with the analysis: running as different users on a shared machine has left temp files
inaccessible.  The JSP code is from Jasper via Jetty.  There may be configuration options
via that route. There may be something that can be added to the Jetty configuration.

In v0.2.1, you can pass in a Jetty config file.

A/ Set the tmp directory to a user-specific one when running Fuseki.
    Modify the fuseki-server script.

B/ delete the tmp area on exit using the shell "on exit" features (from experience, not perfect).

C/ Run a clearup to delete tmp directories before Fuseki.

D/ Run setuid.

A looks the best to me: modify the fuseki-server script to set the tmp directory for the java
process - but of course, two users running two copies may still port-clash.  C and D imply
 imply setuid/sudo programs.

Propose to close this as "not a bug".

> 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