logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-174) Multiple instances of same application server cause 2 problems - want to know if they are solved in log4j 2
Date Fri, 08 Mar 2013 18:52:13 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597393#comment-13597393
] 

Ralph Goers commented on LOG4J2-174:
------------------------------------

There is one case where the RollingFileAppender could lock. It is the case where the file
doesn't actually roll (which Log4j 2 doesn't currently support but I have been planning to
add).

In short, if you do not specify a fileName then the appender should use the file pattern to
create the file to write to. When it is time to roll the appender will simply create a new
file and start writing to it and then delete the oldest file if more than the max number of
files are present. Note that in this case the file cannot be compressed because other JVMs
might still be writing to it.
                
> 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


Mime
View raw message