Alexander Khokhlov created LOG4J2-381:
-----------------------------------------
Summary: Changes in SizeBasedTriggeringPolicy has no effects when
automatic reconfiguration is on.
Key: LOG4J2-381
URL: https://issues.apache.org/jira/browse/LOG4J2-381
Project: Log4j 2
Issue Type: Bug
Components: Appenders
Affects Versions: 2.0-beta8, 2.0-beta9
Reporter: Alexander Khokhlov
My config is very simple:
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
strict="true" monitorInterval="5">
<appenders>
<appender type="console" name="CONSOLE">
<layout type="PatternLayout" pattern="%5p %10c %C{1}(%L) - %m%n"/>
</appender>
<appender name="BOOT" type="rollingfile" fileName="boot.log"
filePattern="boot-%i.log" append="true">
<layout type="PatternLayout" pattern="%5p %10c %C{1}(%L) - %m %ex%n"/>
<SizeBasedTriggeringPolicy size="1 kb" />
<DefaultRolloverStrategy />
</appender>
</appenders>
<loggers>
<root level="all">
<appender-ref ref="CONSOLE"/>
<appender-ref ref="BOOT"/>
</root>
</loggers>
</configuration>
This is because when you create a RollingFileAppender again it uses the
previously created RollingFileManager obtained from MAP (AbstractManager (69)).
But in my case, the name is already exists, so appropriate manager already been
created. But "data" parameter are not the same when manager was created at
first time. It contains new value of policy.
--
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: [email protected]
For additional commands, e-mail: [email protected]
