No Output Folder found

[Joerg Bencke]

Hi folks,

we just installed a fresh Confluence 3.5.13 on an SLES11 / Tmcat 6 / JDK 1.6.035. Setupprocedure went through fine. "You may now start using confluence ....."

We get an error 500 : No output folder

Further detail : tomcat6/work/Catalina/localhost/confluence/org/apache/jsp/default_jsp.java not found

(The path "tomcat6/work/Catalina/localhost/confluence" ends there. only the file "confluence.xml" is listed there, setting the docbase to the correct folder.

Any ideas ?

[Radu Dumitriu · Accepted solution]

Tomcat6 on SLES11 has incorrect permissions set. I fixed that once by installing my own Tomcat in /opt/tomcat and granting corerct permissions to directories.

remove that default RPM and rely on the downloaded version. It's faster to set up.

[Jobin Kuruvilla [Adaptavist]]

Stop Confluence, delete the work directory, restart Confluence and see if the issue persists!

[Joerg Bencke]

With the suse installation, there are two directories there "Catalina" and temp. Deleting the contents of work kills those file as well - breaking to links in the tomcat installation. Had to be created manually again, but no fix for the solution.

Chaging group or user:group to tomcatuser @ "work" does not change problem either

[Jobin Kuruvilla [Adaptavist]]

Check if the Confluence user has all the permission in the installation and home directory. It is possible that you installed Confluence as one user and running it as another without granting enough permissions.

[Joerg Bencke]

tomcat is running as "tomcat" - installationdir & datadir are all "tomcat:tomcat" and "rwx" (via chown -R, so it should be done for all.

the tomcat-dirs however are set to root (Suse standardinstall). Changing it to tomcat:tomcat does not solve the problem, still "default_jsp.java not found" as root cause.

"First" message, btw, is "unable to compile class for jsp"
The strange thing is - the setup process went through fine