The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

log4j.properties for tomcat container does not work with the jira war install

Gary Maxwell
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 11, 2013

I recently installed the latest Jira war install and I am not able to implement the log4.properties for the tomcat container. The log4j.properties configuration for Jira is working great however I am not able to use the tomcat 7 /lib/log4j.properties for the catalina.out log. I am configuring the log4j.properties file so that the catalina out file can be rotated. Does anyone know why this is happening? Is it because of the slf4j jar files that come with jira? Is there a work around?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Christoph Lechleitner
Contributor
March 4, 2013

I just had a similar problem while migrating a hosting customer's Jira 4.0 to a new server using our tomcat 7 debian-package (see https://confluence.clazzes.org/x/wwAj).

The solution is to update the log4j properties file in the jira war file with the customized logj4.properties from jira/webapps/jira/WEB-INF/classes/log4j.properties, like this:

cd /opt/jira/webapps/jira

jar uf ../../installation/atlassian-jira-4.0.war WEB-INF/classes/log4j.properties

TAGS
AUG Leaders

Atlassian Community Events