Tomcat 5.0 notes

Added by Rosie Jameson, last edited by Michelle de Guzman on Oct 22, 2006  (view change)
JIRA Documentation

Index

A user writes: 

In the attached localhost_2006-09-22.log, I can see the first exception has the following:

Caused by: java.security.AccessControlException: access denied (java.io.FilePermission atlassian-jira.log write)
	at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
	at java.security.AccessController.checkPermission(AccessController.java:401)
	at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
	at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:169)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
	at org.apache.log4j.FileAppender.setFile(FileAppender.java:272)
(...)

...and I traced its cause down to Catalina.policy, which, on my platform (Debian/Ubuntu) required me to create the file /etc/tomcat5/policy.d/05jira.policy with the following content:

grant codeBase "file:${catalina.home}/webapps/jira/-" {
  permission java.security.AllPermission;
};

After I "fixed" this issue, I then needed to chown tomcat5 $JIRA_HOME -R otherwise the HSQL database couldn't be created.

A user writes: 

There is a readme file shipped with JIRA. It said that you need to change port 8080 in order to get Tomcat(say a) to start up. BUT, if you have a CATALINA_HOME environment variable already set for an existing Tomcat(say b) running on the same server, running startup from the bin directory will start up Tomcat(b). For Tomcat(a) to start one needs to delete the existing CATALINA_HOME environment variable as well.

Labels

 
(None)