On Linux Fuseki will create user owned temporary files that block other users 
from running Fuseki instances even after the Fuseki instance has been stopped
-----------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JENA-179
                 URL: https://issues.apache.org/jira/browse/JENA-179
             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 correctly.

Going to the control panel will produce the following trace:

Error 500: /tmp/org/apache/jsp/control_002dpanel_jsp.java (Permission denied)

java.io.FileNotFoundException: /tmp/org/apache/jsp/control_002dpanel_jsp.java 
(Permission denied)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
        at 
org.apache.jasper.compiler.JDTJavaCompiler.getJavaWriter(JDTJavaCompiler.java:149)
        at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:188)
        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:435)
        at 
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:608)
        at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:360)
        at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:534)
        at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:475)
        at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:224)
        at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:921)
        at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:403)
        at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:184)
        at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:856)
        at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)
        at org.eclipse.jetty.server.Server.handle(Server.java:348)
        at 
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:596)
        at 
org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1052)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:590)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:212)
        at 
org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426)
        at 
org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:292)
        at 
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:450)
        at java.lang.Thread.run(Thread.java:619)



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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to