Unable to use RollingFileAppender
Hello, I'm new to logback but read your documentation, I an not receiving any output to my logfile. Here is my configuration file, following this is the output from logback to the console. The only thing I notice is a warning about a TriggerPolicy. If this is the case do you have example syntax? --- <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <param name="append" value="true"/> <param name="MaxBackupIndex" value="1"/> <param name="file" value="/tmp/bitran.log"/> <param name="MaxFileSize" value="5MB"/> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%d [%-15.15t] %-5p %-30.30c{1} - %m%n"/> </layout> </appender> <logger name="org.accma.concentrator.services.bitran.BiTranService" additivity="false"> <level value="debug"/> <appender-ref ref="bitranlog"/> </logger> <root> <level value="debug" /> <appender-ref ref="bitranlog" /> </root> </configuration> --- Here is console output when using LoggerStatusPrinter: --- startElement [configuration] startElement [appender] startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@8c5ea2 startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@198defc startElement [layout] startElement [param] startElement [logger] startElement [level] startElement [appender-ref] startElement [root] startElement [level] startElement [appender-ref] INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch .qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from t he object stack INFO in ch.qos.logback.classic.joran.action.LevelAction - org.accma.concentrator.services.bitran.Bi TranService level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[org.accma.concentrator.services.bitran.BiTranService] INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[root] Thanks, S.D.
Hello Samuel, Thanks for trying logback! The RollingFileAppender needs a TriggeringPolicy object to know when to roll the active output file. In brief, a TriggeringPolicy controls the conditions under which roll-over occurs. Such conditions include time of day, file size, an external event, the log request or a combination thereof. A working configuration file for a RollingFileAppender would be: <configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <param name="File" value="/path/to/your/file.log"/> <rollingPolicy class="ch.qos.logback.core.rolling.SizeBasedRollingPolicy"> <param name="MaxFileSize" value="5MB" /> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="Pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="FILE" /> </root> </configuration> With this configuration, the file would be rolled each time it reaches 5MB. When I look at the configuration file that you sent, something seems strange to me: Why do you configure two Loggers with the same Appender and one of them with the Additivity flag set to false? One would obtain the same result simply by attaching the RollingFileAppender to the root logger. Hope this helps you get on track with logback. Do not hesitate to write again if you run into trouble. Sébastien -- Sébastien Pennec sebastien@qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. Samuel Doyle a écrit :
Hello,
I'm new to logback but read your documentation, I an not receiving any output to my logfile. Here is my configuration file, following this is the output from logback to the console. The only thing I notice is a warning about a TriggerPolicy. If this is the case do you have example syntax? ---
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <param name="append" value="true"/> <param name="MaxBackupIndex" value="1"/> <param name="file" value="/tmp/bitran.log"/> <param name="MaxFileSize" value="5MB"/> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%d [%-15.15t] %-5p %-30.30c{1} - %m%n"/> </layout> </appender>
<logger name="org.accma.concentrator.services.bitran.BiTranService" additivity="false"> <level value="debug"/> <appender-ref ref="bitranlog"/> </logger>
<root> <level value="debug" /> <appender-ref ref="bitranlog" /> </root>
</configuration>
--- Here is console output when using LoggerStatusPrinter: ---
startElement [configuration] startElement [appender] startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@8c5ea2 startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@198defc startElement [layout] startElement [param] startElement [logger] startElement [level] startElement [appender-ref] startElement [root] startElement [level] startElement [appender-ref] INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch .qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from t he object stack INFO in ch.qos.logback.classic.joran.action.LevelAction - org.accma.concentrator.services.bitran.Bi TranService level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[org.accma.concentrator.services.bitran.BiTranService] INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[root]
Thanks, S.D.
------------------------------------------------------------------------
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Hello Sebastien, Excellent, I will give this a try. Thanks for your response. S.D. Sebastien Pennec <sebastien@qos.ch> wrote: Hello Samuel, Thanks for trying logback! The RollingFileAppender needs a TriggeringPolicy object to know when to roll the active output file. In brief, a TriggeringPolicy controls the conditions under which roll-over occurs. Such conditions include time of day, file size, an external event, the log request or a combination thereof. A working configuration file for a RollingFileAppender would be: With this configuration, the file would be rolled each time it reaches 5MB. When I look at the configuration file that you sent, something seems strange to me: Why do you configure two Loggers with the same Appender and one of them with the Additivity flag set to false? One would obtain the same result simply by attaching the RollingFileAppender to the root logger. Hope this helps you get on track with logback. Do not hesitate to write again if you run into trouble. Sébastien -- Sébastien Pennec sebastien@qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. Samuel Doyle a écrit :
Hello,
I'm new to logback but read your documentation, I an not receiving any output to my logfile. Here is my configuration file, following this is the output from logback to the console. The only thing I notice is a warning about a TriggerPolicy. If this is the case do you have example syntax? ---
class="ch.qos.logback.core.rolling.RollingFileAppender">
additivity="false">
--- Here is console output when using LoggerStatusPrinter: ---
startElement [configuration] startElement [appender] startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@8c5ea2 startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@198defc startElement [layout] startElement [param] startElement [logger] startElement [level] startElement [appender-ref] startElement [root] startElement [level] startElement [appender-ref] INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch .qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from t he object stack INFO in ch.qos.logback.classic.joran.action.LevelAction - org.accma.concentrator.services.bitran.Bi TranService level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[org.accma.concentrator.services.bitran.BiTranService] INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[root]
Thanks, S.D.
------------------------------------------------------------------------
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Samuel, You can also trigger rollover based on date. Do not hesitate to ping us if you would like an example of trigger based on time. Cheers, At 07:17 PM 9/13/2006, Samuel Doyle wrote:
Hello Sebastien,
Excellent, I will give this a try. Thanks for your response.
S.D.
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/
Hi, using this it is now complaining about a triggeringpolicy. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] ERROR in ch.qos.logback.core.joran.action.NestedComponentIA - Could not create component <rollingPolicy>. WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from the object stack Sebastien Pennec <sebastien@qos.ch> wrote: Hello Samuel, Thanks for trying logback! The RollingFileAppender needs a TriggeringPolicy object to know when to roll the active output file. In brief, a TriggeringPolicy controls the conditions under which roll-over occurs. Such conditions include time of day, file size, an external event, the log request or a combination thereof. A working configuration file for a RollingFileAppender would be: With this configuration, the file would be rolled each time it reaches 5MB. When I look at the configuration file that you sent, something seems strange to me: Why do you configure two Loggers with the same Appender and one of them with the Additivity flag set to false? One would obtain the same result simply by attaching the RollingFileAppender to the root logger. Hope this helps you get on track with logback. Do not hesitate to write again if you run into trouble. Sébastien -- Sébastien Pennec sebastien@qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. Samuel Doyle a écrit :
Hello,
I'm new to logback but read your documentation, I an not receiving any output to my logfile. Here is my configuration file, following this is the output from logback to the console. The only thing I notice is a warning about a TriggerPolicy. If this is the case do you have example syntax? ---
class="ch.qos.logback.core.rolling.RollingFileAppender">
additivity="false">
--- Here is console output when using LoggerStatusPrinter: ---
startElement [configuration] startElement [appender] startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@8c5ea2 startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@198defc startElement [layout] startElement [param] startElement [logger] startElement [level] startElement [appender-ref] startElement [root] startElement [level] startElement [appender-ref] INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch .qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from t he object stack INFO in ch.qos.logback.classic.joran.action.LevelAction - org.accma.concentrator.services.bitran.Bi TranService level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[org.accma.concentrator.services.bitran.BiTranService] INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[root]
Thanks, S.D.
------------------------------------------------------------------------
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Hello Samuel, I'd try the following. (Apologies, I did not have time to test it, so it might contain minor mistakes.) <appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <param name="ActiveFile" value="bitran.log" /> <param name="FileNamePattern" value="bitran.%i.log" /> <param name="MinIndex" value="1" /> <param name="MaxIndex" value="3" /> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedRollingPolicy"> <param name="MaxFileSize" value="5MB" /> </triggeringPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> The TimeBasedRollingPolicy based example that you would usually want to use in real life (instead of the above) is less verbose, and just as powerful. <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <param name="FileNamePattern" value="foo_%d{yyyy-MM}.log".zip /> <param name="ActiveFileName" value="foo.log" /> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="Pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> You might also want to have a look at the javadocs. http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/SizeBasedTriggerin... http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/FixedWindowRolling... http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/TimeBasedRollingPo... If you run into problems, please let us know. At 08:24 PM 9/14/2006, Samuel Doyle wrote:
Hi, using this it is now complaining about a triggeringpolicy.
INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] ERROR in ch.qos.logback.core.joran.action.NestedComponentIA - Could not create component <rollingPolicy>. WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from the object stack
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/
Great, this works fine. S.D. Ceki Gülcü <listid@qos.ch> wrote: Hello Samuel, I'd try the following. (Apologies, I did not have time to test it, so it might contain minor mistakes.) class="ch.qos.logback.core.rolling.RollingFileAppender"> class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> class="ch.qos.logback.core.rolling.SizeBasedRollingPolicy"> The TimeBasedRollingPolicy based example that you would usually want to use in real life (instead of the above) is less verbose, and just as powerful. class="ch.qos.logback.core.rolling.RollingFileAppender"> You might also want to have a look at the javadocs. http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/SizeBasedTriggerin... http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/FixedWindowRolling... http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/TimeBasedRollingPo... If you run into problems, please let us know. At 08:24 PM 9/14/2006, Samuel Doyle wrote:
Hi, using this it is now complaining about a triggeringpolicy.
INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] ERROR in ch.qos.logback.core.joran.action.NestedComponentIA - Could not create component . WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from the object stack
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/ _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
Hello all, Just a quick correction on the last sent configuration file (first example). There was a misspelled class name that should be corrected before the config can be used as-is. Here is the config file that I've just tested and that works: <configuration> <appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <param name="ActiveFileName" value="bitran.log" /> <param name="FileNamePattern" value="bitran.%i.log" /> <param name="MinIndex" value="1" /> <param name="MaxIndex" value="3" /> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <param name="MaxFileSize" value="5MB" /> </triggeringPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="Pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="FILE" /> </root> </configuration> Sébastien Ceki Gülcü a écrit :
Hello Samuel,
I'd try the following. (Apologies, I did not have time to test it, so it might contain minor mistakes.)
<appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <param name="ActiveFile" value="bitran.log" /> <param name="FileNamePattern" value="bitran.%i.log" /> <param name="MinIndex" value="1" /> <param name="MaxIndex" value="3" /> </rollingPolicy>
<triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedRollingPolicy"> <param name="MaxFileSize" value="5MB" /> </triggeringPolicy>
<layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender>
The TimeBasedRollingPolicy based example that you would usually want to use in real life (instead of the above) is less verbose, and just as powerful.
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <param name="FileNamePattern" value="foo_%d{yyyy-MM}.log".zip /> <param name="ActiveFileName" value="foo.log" /> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="Pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender>
You might also want to have a look at the javadocs.
http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/SizeBasedTriggerin...
http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/FixedWindowRolling...
http://logback.qos.ch/apidocs/ch/qos/logback/core/rolling/TimeBasedRollingPo...
If you run into problems, please let us know.
At 08:24 PM 9/14/2006, Samuel Doyle wrote:
Hi, using this it is now complaining about a triggeringpolicy.
INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] ERROR in ch.qos.logback.core.joran.action.NestedComponentIA - Could not create component <rollingPolicy>. WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from the object stack
-- Sébastien Pennec sebastien@qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java.
Hi, here is the exact configuration I'm using now. <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <param name="File" value="bitran.log" /> <rollingPolicy class="ch.qos.logback.core.rolling.SizeBasedRollingPolicy"> <param name="MaxFileSize" value="5MB" /> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%-4relative [%thread] %-5level %class - %msg%n" /> </layout> </appender> <logger name="org.accma.concentrator.services.bitran.BiTranService"> <level value="debug"/> <appender-ref ref="bitranlog"/> </logger> <root> <level value="debug" /> <appender-ref ref="STDOUT" /> </root> </configuration> ~ Sebastien Pennec <sebastien@qos.ch> wrote: Hello Samuel, Thanks for trying logback! The RollingFileAppender needs a TriggeringPolicy object to know when to roll the active output file. In brief, a TriggeringPolicy controls the conditions under which roll-over occurs. Such conditions include time of day, file size, an external event, the log request or a combination thereof. A working configuration file for a RollingFileAppender would be: With this configuration, the file would be rolled each time it reaches 5MB. When I look at the configuration file that you sent, something seems strange to me: Why do you configure two Loggers with the same Appender and one of them with the Additivity flag set to false? One would obtain the same result simply by attaching the RollingFileAppender to the root logger. Hope this helps you get on track with logback. Do not hesitate to write again if you run into trouble. Sébastien -- Sébastien Pennec sebastien@qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. Samuel Doyle a écrit :
Hello,
I'm new to logback but read your documentation, I an not receiving any output to my logfile. Here is my configuration file, following this is the output from logback to the console. The only thing I notice is a warning about a TriggerPolicy. If this is the case do you have example syntax? ---
class="ch.qos.logback.core.rolling.RollingFileAppender">
additivity="false">
--- Here is console output when using LoggerStatusPrinter: ---
startElement [configuration] startElement [appender] startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@8c5ea2 startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@198defc startElement [layout] startElement [param] startElement [logger] startElement [level] startElement [appender-ref] startElement [root] startElement [level] startElement [appender-ref] INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch .qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from t he object stack INFO in ch.qos.logback.classic.joran.action.LevelAction - org.accma.concentrator.services.bitran.Bi TranService level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[org.accma.concentrator.services.bitran.BiTranService] INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[root]
Thanks, S.D.
------------------------------------------------------------------------
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user
participants (3)
-
Ceki Gülcü -
Samuel Doyle -
Sebastien Pennec