Current development on JAMWiki is primarily focused on maintenance rather than new features due to a lack of developer availability. If you are interested in working on JAMWiki please join the jamwiki-devel mailing list.

Comments:JAMWiki 0.8.2

Problems installing JamWiki[edit]

During the start of the deployed jamwiki-0.8.2.war application, I got the following message in catalina.out:

08.02.2010 18:42:24 org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive jamwiki-0.8.2.war
WARNING: Unable to load custom JAMWiki logging configuration, using system default access denied (java.util.logging.LoggingPermission control)
08.02.2010 18:42:29 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error listenerStart
08.02.2010 18:42:29 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [/jamwiki-0.8.2] startup failed due to previous errors

Any ideas? I can't find any clue. The Error "Error listenerStart" says nothing!

I'm not 100% sure, but if I had to guess I'd say that JAMWiki doesn't have permission to write to its log file. Take a look at the /WEB-INF/classes/logging.properties and verify that JAMWiki has write permission for the file/directory specified by the org.jamwiki.pattern value. -- Ryan • (comments) • 08-Feb-2010 12:55 PST
The error message above is due to invalid permissions on the logging directory. That of itself should not cause a deployment to fail (it will default to System.out), so it's possible there may be other permission problems in the environment. -- Ryan • (comments) • 08-Feb-2010 21:05 PST
Is there a list of directories where write permission is necessary? Is there another log file wich contains detailed error messages? The tomcat server runs on the server of my provider. So I've limited access. Regards --Andreas 10-Feb-2010 06:44 PST
Have a look at Installation#New Installs, which details directories used. -- Ryan • (comments) • 10-Feb-2010 07:50 PST
My provider starts the tomcat in security mode (command line option -security). The logging problem needs the following permission in file tomcat/conf/catalina.policy: java.util.logging.LoggingPermission "control"; Are there any other permissions needed? I can't get any clue to the problem, because no explicit error message is written... :-/ Thanx!!! --Andreas 15-Feb-2010 05:13 PST
I'll need to defer to others who better understand SELinux to say what permissions are required. Searching online indicates that most people eventually give up and go with java.security.AllPermission, something your provider may not allow. I'll see if there is anywhere that I can add additional logging for future releases, but otherwise I'm not sure if I can be of any additional help (sorry!). If you do figure it out then any updates would be much appreciated. -- Ryan • (comments) • 15-Feb-2010 10:34 PST