Title | Fails to load on Ubuntu / Dapper install |
Date | 21-Jun-2006 17:16:24 EEST |
Version | v2.2.33 |
Submitter | 80.254.166.97 |
Bug criticality | FatalBug |
Browser version | Firefox |
Bug status | ClosedBug |
PageProvider used | |
Servlet Container | Tomcat 5.0 |
Operating System | Ubuntu |
URL | Any, e.g. .../Error.jsp |
Java version | 1.5 |
I get the followin error when trying to load any page. I had a version installed on a previous version of Ubuntu and it worked fine. I've written a JSP to check that the jspwiki.properties can be loaded through a getResourceAsStream and I can retrieve properties fine. I guess it's a permissions problem but for which directory? Tomcat is running as root too.
I'm still working on it but if anyone has a quick fix!!
2006-06-21 15:49:28 StandardContext[]Application 27270794 requests WikiEngine. 2006-06-21 15:49:28 StandardContext[] Assigning new log to 27270794 2006-06-21 15:49:28 StandardContext[]No jspwiki.propertyfile defined for this context, using default from /WEB-INF/jspwiki.properties 2006-06-21 15:49:28 StandardContext[]ERROR: Failed to create a Wiki engine: access denied (java.util.PropertyPermission user.dir read) 2006-06-21 15:49:28 StandardContext[]Application 27270794 requests WikiEngine. 2006-06-21 15:49:28 StandardContext[] Assigning new log to 27270794 2006-06-21 15:49:28 StandardContext[]No jspwiki.propertyfile defined for this context, using default from /WEB-INF/jspwiki.properties 2006-06-21 15:49:28 StandardContext[]ERROR: Failed to create a Wiki engine: access denied (java.util.PropertyPermission user.dir read) 2006-06-21 15:49:28 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception com.ecyrd.jspwiki.InternalWikiException: No wiki engine, check logs. at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:293) at com.ecyrd.jspwiki.WikiEngine.getInstance(WikiEngine.java:240) at org.apache.jsp.atom_jsp.jspInit(atom_jsp.java:19) at org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:75)
This seems like a policy problem. Check your Java policy file that you're giving proper permissions to Tomcat to access the directory?
Thanks Janne. The error turned out to be an RFM problem. The Ubuntu (and I guess Debian too) installation of Tomcat comes with the security manager enabled (I don't think it was in the older version I used). This can be disabled in the /etc/default/tomcat5 file. Here's the snippit from the tomcat5 install doc:
- Tomcat is started using a security manager, you can define the permissions for your servlets and JSPs in /etc/tomcat5/policy.d/*. All files in this directory are joined to /etc/tomcat5/catalina.policy at startup. If your webapp does not work with the tomcat5 Debian package but works fine with the binary distribution from Jakarta, try to disbale the security manager in /etc/default/tomcat5 first. If this works, add the required permissions in a new file in /etc/tomcat5/policy.d/ restart and re-enable the security manager. Disabling the security manager is not recommended on production systems since a call to System.exit() in a servlet of JSP page would then stop the whole virtual machine that is running Tomcat.
Thanks Keith, closing!
-- JanneJalkanen, 24-Sep-2006
As an addition to the note of Keith: The Security Manager in Tomcat on ubuntu can be turned of by setting the property TOMCAT5_SECURITY = no in the startup file of the tomcat server: /etc/init.d/tomcat5.5
Daniel Seiler
Hi -- JSPWiki doesn't yet play nicely inside a SecurityManager (ironic, I know). We are working on this, but we won't have the full set of required permissions enumerated for a while. So your workaround is the right thiing to do.
--AndrewJaquith, 28-Feb-2007
It turns out that all the way up to Gutsy - because it doesn't deploy a *.war file it stuff up.
Suppose you go
apt-get install jspwiki
Then you still need to create:
/usr/share/tomcat5.5/conf/Catalina/localhost/jspwiki.xmlwith the following contents
<!-- Context configuration file for the JSPWiki --> <Context path="/jspwiki" docBase="/usr/share/jspwiki" debug="0" privileged="true" allowLinking="true"> </Context>
Then do
/etc/init.d/tomcat5.5 restart
Before you can really do anything. This is effectively a bug in the Debian/Ubuntu package distribution.
This page is really useful too :http://roshan18.wordpress.com/2007/11/18/using-servlets-in-ubuntu-gutsy-gibbon/
--AnonymousCoward, 24-May-2008
Problem of indexation of the graphic file PNG, impossible to start JSPWIKI(UBUNTU - Hardy Heron )#
I fallow all the instructions. Everything run well until i move all the JSP Content v2.2.3 to the new one 2.5.139-1 When a move the 2.2.3 content into the /var/lib/jspwiki/default, impossible to start! i got this message:SEVERE: Error filterStartJspwiki seems faild to index when the extensions are in uppercase like PNG fo exemple.
This message is probably from Lucent and should be sent to jspwiki exception...
--elannaud, 10-sept.-2008 18:23
Personally I consider a web-app not running with tomcat security manager a grave bug. Lack of support for tomcat security manager is a show-stopper in production environments.
--AnonymousCoward, 03-march-2009 20:55