You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Jas Gill (JIRA)" <ji...@apache.org> on 2013/03/07 17:56:14 UTC

[jira] [Created] (LOG4J2-174) Multiple instances of same application server cause 2 problems - want to know if they are solved in log4j 2

Jas Gill created LOG4J2-174:
-------------------------------

             Summary: Multiple instances of same application server cause 2 problems - want to know if they are solved in log4j 2
                 Key: LOG4J2-174
                 URL: https://issues.apache.org/jira/browse/LOG4J2-174
             Project: Log4j 2
          Issue Type: Question
          Components: Appenders
         Environment: Unix based OS and Java based application servers
            Reporter: Jas Gill


When we start multiple instances of application server using log4j 1.2 and all instances read same configuration file, two problems are noticed. 

1. At rollover time first app server doing rollover will do its job properly but when subsequent ones will do rollover again and we lose logs. May be log4j should check that if rolled over file is already present, it should skip rollover.
2. After rollover only one instance is logging and others stop logging. The problem is that the active file was rolled over and new file is created. Only one server has pointer to it.

	<appender name="ROLLING" class="org.apache.log4j.rolling.RollingFileAppender">
		<param name="Threshold" value="ALL"/>
		<param name="Append" value="true" />	
		<rollingPolicy name="CONSOLE" class="org.apache.log4j.rolling.TimeBasedRollingPolicy">
			<param name="FileNamePattern" value="${LOG_FILE}.%d{yyyy-MM-dd-HH-mm}" />
			<param name="ActiveFileName" value="${LOG_FILE}" />					
		</rollingPolicy>
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern" value="%d{ISO8601} %-5p [%t]%x %c{2} - %m%n"/>
		</layout>
	</appender>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org