- logback-dev - mailman3.qos.ch

[qos-ch/logback-audit] 1e5bae: typo fix
by Ceki Gulcu 21 Feb '13

21 Feb '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-audit Commit: 1e5baea7a0e687b874ce45d6d11539055fc3f697 https://github.com/qos-ch/logback-audit/commit/1e5baea7a0e687b874ce45d6d115… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-02-21 (Thu, 21 Feb 2013) Changed paths: M audit-site/src/site/pages/faq.html Log Message: ----------- typo fix Commit: 19b14868bc7ba35fc271f0f64c4f029f57728192 https://github.com/qos-ch/logback-audit/commit/19b14868bc7ba35fc271f0f64c4f… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-02-21 (Thu, 21 Feb 2013) Changed paths: M audit-site/src/site/pages/bugreport.html M audit-site/src/site/pages/faq.html M audit-site/src/site/pages/manual/Invoking_lba.html M audit-site/src/site/pages/manual/Running_the_Server.html M audit-site/src/site/pages/manual/index.html M audit-site/src/site/pages/manual/introduction.html Log Message: ----------- update css links Compare: https://github.com/qos-ch/logback-audit/compare/13f760ccc083...19b14868bc7b

1 0

Re : stop() and start() on LoggerContext
by Mathieu Stempell 21 Feb '13

21 Feb '13

Replying to myself as i found the solution over the web. I had to call LoggerContext reset() and then ContextInitializer autoConfig() for the logging to be effective again after LoggerContext stop() & start(), as described here : http://stackoverflow.com/a/3810936 Mathieu ----- Message d'origine ----- De : Mathieu Stempell Envoyés : 20.02.13 15:28 À : logback-dev(a)qos.ch Objet : [logback-dev] stop() and start() on LoggerContext Hello, When i call start() method on LoggerContext after i called stop(), i doesn't log anything new in the output files : ----------- LoggerContext loggerContext = (LoggerContext)LoggerFactory.getILoggerFactory(); LoggerFactory.getLogger(AbstractTest.class).info("test info before stop"); // logs, ok loggerContext.stop(); LoggerFactory.getLogger(AbstractTest.class).info("test info between stop and start"); // doesn't log, ok loggerContext.start(); LoggerFactory.getLogger(AbstractTest.class).info("test info after start"); // doesn't log, why??? ----------- Is it normal or not? Thanks in advance for your anwser. Mathieu

1 0

stop() and start() on LoggerContext
by Mathieu Stempell 20 Feb '13

20 Feb '13

Hello, When i call start() method on LoggerContext after i called stop(), i doesn't log anything new in the output files : ----------- LoggerContext loggerContext = (LoggerContext)LoggerFactory.getILoggerFactory(); LoggerFactory.getLogger(AbstractTest.class).info("test info before stop"); // logs, ok loggerContext.stop(); LoggerFactory.getLogger(AbstractTest.class).info("test info between stop and start"); // doesn't log, ok loggerContext.start(); LoggerFactory.getLogger(AbstractTest.class).info("test info after start"); // doesn't log, why??? ----------- Is it normal or not? Thanks in advance for your anwser. Mathieu

1 0

[JIRA] Created: (LBCORE-200) Add possibility to mark included file/resource optional
by Attila Király (JIRA) 20 Feb '13

20 Feb '13

Add possibility to mark included file/resource optional ------------------------------------------------------- Key: LBCORE-200 URL: http://jira.qos.ch/browse/LBCORE-200 Project: logback-core Issue Type: Improvement Components: Joran Affects Versions: 0.9.28 Reporter: Attila Király Assignee: Logback dev list Priority: Minor It would be nice if an <include /> element could be marked as optional. So if the file/resource is not found no error is logged about it (as it is now). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 1

[JIRA] (LOGBACK-794) If no config file is found, no debug info is printed
by Antony Stubbs (JIRA) 18 Feb '13

18 Feb '13

3 4

[JIRA] (LOGBACK-717) If no config file is found, no debug info is printed out, even with logback.debug=true sys prop
by Antony Stubbs (JIRA) 18 Feb '13

18 Feb '13

4 21

[JIRA] Created: (LBCORE-188) Log Rotation/Gzip process leaving .tmp files behind
by Bert B-L (JIRA) 18 Feb '13

18 Feb '13

Log Rotation/Gzip process leaving .tmp files behind --------------------------------------------------- Key: LBCORE-188 URL: http://jira.qos.ch/browse/LBCORE-188 Project: logback-core Issue Type: Bug Components: Rolling Affects Versions: 0.9.26 Reporter: Bert B-L Assignee: Logback dev list We are seeing logback leave .tmp files behind in the log directory, presumably due to a hiccup during log rotation or gzip. Size 2365956 Dec 11 00:00 statsreceiver.log.2010-12-10.gz 2679618 Dec 12 00:01 statsreceiver.log.2010-12-11.gz 9190879942 Dec 12 04:00 statsreceiver-debug.log23124507802228260.tmp 2542799 Dec 13 00:00 statsreceiver.log.2010-12-12.gz 9137740366 Dec 13 04:00 statsreceiver-debug.log23210907242250260.tmp 543937393 Dec 13 20:07 statsreceiver-debug.log.2010-12-13_19:00.gz 548781049 Dec 13 22:07 statsreceiver-debug.log.2010-12-13_21:00.gz 2284216 Dec 14 00:00 statsreceiver.log.2010-12-13.gz 8127562 Dec 15 00:00 statsreceiver.log.2010-12-14.gz 19067117496 Dec 15 13:00 statsreceiver-debug.log23416102512001260.tmp 18177324477 Dec 15 16:00 statsreceiver-debug.log23426920509229260.tmp 2257423 Dec 15 23:00 statsreceiver-debug.log.2010-12-15_22:00.gz The logback jar versions are: WEB-INF/lib/logback-classic-0.9.26.jar WEB-INF/lib/logback-core-0.9.26.jar There is only a single application writing to those files, though it is conceivable that the .tmp droppings correlate to restarts of that application. If this is expected on application restarts, could logback start gzip'ing them again when it comes back? Here is the logback.xml file: <?xml version="1.0" encoding="UTF-8"?> <configuration scan="true" scanPeriod="60 seconds"> <appender name="FILE_WARN" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logdir:-.}/${prog:-unknown}.log</file> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>warn</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${logdir:-.}/${prog:-unknown}.log.%d{yyyy-MM-dd}.gz</fileNamePattern> <maxHistory>7</maxHistory> </rollingPolicy> <encoder> <pattern>%-30(%d{yyyy-MM-dd HH:mm:ss} %.-1level :) %m Context:[%X{GTNDC_INFO}]%n</pattern> </encoder> </appender> <appender name="FILE_DEBUG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${logdir:-.}/${prog:-unknown}-debug.log</file> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>debug</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${logdir:-.}/${prog:-unknown}-debug.log.%d{yyyy-MM-dd_HH:00}.gz</fileNamePattern> <maxHistory>36</maxHistory> </rollingPolicy> <encoder> <pattern>%-60(%d{yyyy-MM-dd HH:mm:ss} [%thread] %.-1level :) %m Context:[%X{GTNDC_INFO}]%n</pattern> </encoder> </appender> <logger name="org.apache.directory" level="WARN"/> <root><level value="debug"/> <appender-ref ref="FILE_WARN"/> <appender-ref ref="FILE_DEBUG"/> </root> </configuration> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

9 21

[qos-ch/logback] e3470d: small fixes to imports section
by Joris Kuipers 17 Feb '13

17 Feb '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: e3470d100ac97f415bdf124950ee3dcfbca3c011 https://github.com/qos-ch/logback/commit/e3470d100ac97f415bdf124950ee3dcfbc… Author: Joris Kuipers <joriskuipers(a)gmail.com> Date: 2013-02-17 (Sun, 17 Feb 2013) Changed paths: M logback-site/src/site/pages/manual/groovy.html Log Message: ----------- small fixes to imports section

1 0

[qos-ch/logback] 77cf66: Updated groovy docs to match last commit
by Joris Kuipers 15 Feb '13

15 Feb '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 77cf66e8c48abb5bfef4eb1f3eaca764cc5ec1f0 https://github.com/qos-ch/logback/commit/77cf66e8c48abb5bfef4eb1f3eaca764cc… Author: Joris Kuipers <joriskuipers(a)gmail.com> Date: 2013-02-15 (Fri, 15 Feb 2013) Changed paths: M logback-site/src/site/pages/manual/groovy.html Log Message: ----------- Updated groovy docs to match last commit

1 0

[qos-ch/logback] e43028: added Joris Kuipers
by Ceki Gulcu 14 Feb '13

14 Feb '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: e4302866648adea5969e4431b0bae0e3c3127886 https://github.com/qos-ch/logback/commit/e4302866648adea5969e4431b0bae0e3c3… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-02-14 (Thu, 14 Feb 2013) Changed paths: M src/main/clas/signed-clas.txt Log Message: ----------- added Joris Kuipers

1 0