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 "Erik Weathers (JIRA)" <ji...@apache.org> on 2017/02/28 01:52:45 UTC

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

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

Erik Weathers commented on LOG4J2-174:
--------------------------------------

hi [~ralphgoers] or [~ralph.goers@dslextreme.com]  (kind of frustrating having 3 different names in the JIRA autocomplete!).

I found the above comments from you to be a bit conflicting.  I believed log4j 2 to be an improvement across the board beyond logback, so I assumed it would have support for multiple JVMs writing to the same log file, since logback supports that via prudent mode.   I am unclear if this is really unsupported in log4j2 2?

> 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 was sent by Atlassian JIRA
(v6.3.15#6346)

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