May 2012 - logback-dev - mailman3.qos.ch

[qos-ch/logback] ec9f0e: Use locks of type LogbackLock instead of just Obje...
by Ceki Gulcu 22 May '12

22 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: ec9f0e170b5bbe2121e8ac28502ab9f211e8775f https://github.com/qos-ch/logback/commit/ec9f0e170b5bbe2121e8ac28502ab9f211… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-22 (Tue, 22 May 2012) Changed paths: M logback-access/src/main/java/ch/qos/logback/access/tomcat/LogbackValve.java M logback-classic/src/test/java/ch/qos/logback/classic/db/DBAppenderIntegrationTest.java M logback-core/src/main/java/ch/qos/logback/core/BasicStatusManager.java M logback-core/src/main/java/ch/qos/logback/core/ContextBase.java M logback-core/src/main/java/ch/qos/logback/core/OutputStreamAppender.java A logback-core/src/main/java/ch/qos/logback/core/spi/LogbackLock.java Log Message: ----------- Use locks of type LogbackLock instead of just Object for increased clarity when analysing thread dumps

1 0

[JIRA] Created: (LBCLASSIC-240) JNDIUtil.lookup always cast the JNDI lookup result to a String
by Maxence Dewil (JIRA) 22 May '12

22 May '12

JNDIUtil.lookup always cast the JNDI lookup result to a String -------------------------------------------------------------- Key: LBCLASSIC-240 URL: http://jira.qos.ch/browse/LBCLASSIC-240 Project: logback-classic Issue Type: Bug Components: joran Affects Versions: 0.9.27 Reporter: Maxence Dewil Assignee: Logback dev list JNDIUtil.lookup always cast the JNDI lookup result to a String. This method should support other object types like: java.net.URL, ... Description: 1. In our environment, we have declared a variable in Websphere that holds a URL. 2. We use an <insertFromJNDI /> tag. 3. Then the following exception is thrown: ERROR in ch.qos.logback.core.joran.spi.Interpreter@4:71 - RuntimeException in Action for tag [insertFromJNDI] java.lang.ClassCastException: java.net.URL incompatible with java.lang.String at java.lang.ClassCastException: java.net.URL incompatible with java.lang.String at at ch.qos.logback.classic.util.JNDIUtil.lookup(JNDIUtil.java:38) at at ch.qos.logback.classic.joran.action.InsertFromJNDIAction.begin(InsertFromJNDIAction.java:62) at at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:273) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:145) at at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:127) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:40) at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) -- 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

3 13

[JIRA] (LBCLASSIC-331) Console appender may deadlock when System.out is hijacked
by Gunnar Wagenknecht (JIRA) 22 May '12

22 May '12

2 4

[JIRA] Created: (LBCLASSIC-330) no debug info printed when problem with FixedWindowRollingPolicy
by Antony Stubbs (JIRA) 22 May '12

22 May '12

no debug info printed when problem with FixedWindowRollingPolicy ---------------------------------------------------------------- Key: LBCLASSIC-330 URL: http://jira.qos.ch/browse/LBCLASSIC-330 Project: logback-classic Issue Type: Bug Components: joran Reporter: Antony Stubbs Assignee: Logback dev list Priority: Critical This configuration causes no debug output to be displayed: {code} <configuration scan="true" scanPeriod="30 seconds" debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <target>System.out</target> <encoder> <pattern>| [%-5level] [%date{ISO8601}] [%logger] [%thread] [%X{akkaSource}] - %msg %rootException %n</pattern> </encoder>sdfsadf </appender> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>server.log</file>  <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>server.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>3</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>1MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>| [%-5level] [%date{ISO8601}] [%logger] [%thread] [%X{akkaSource}] - %msg %rootException %n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT"/> <appender-ref ref="ROLLING"/> </root> </configuration> {code} If I remove the rolling file appender, debug output is shown. If I remove just the rollingPolicy, debug output is shown. If I remove just the <fileNamePattern>server-event.%i.log</fileNamePattern> the debug output is displayed and the exception about the missing field is shown. Seems related to http://jira.qos.ch/browse/LBCORE-38 and http://jira.qos.ch/browse/LBCLASSIC-62 -- 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 15

[qos-ch/logback] 93f025: correction
by Ceki Gulcu 20 May '12

20 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 93f025b3359b44b931ed1ebde341bdc9bc9f0a43 https://github.com/qos-ch/logback/commit/93f025b3359b44b931ed1ebde341bdc9bc… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-20 (Sun, 20 May 2012) Changed paths: M logback-site/src/site/pages/manual/encoders.html Log Message: ----------- correction

1 0

Invitation to connect on LinkedIn
by jian jin 16 May '12

16 May '12

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - jian jian jin Lead Software Engineer at Yottaa China Confirm that you know jian jin: https://www.linkedin.com/e/51ztqj-h2ah37g5-5i/isd/7120733741/XQF83x0p/?hs=f… -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/51ztqj-h2ah37g5-5i/uDCAGVGkjY84eK9wA0CYeCGzU9Zumf… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

1 0

[JIRA] Created: (LBCLASSIC-318) ConcurrentModificationException when LoggerContext.reset
by Szczepan Faber (JIRA) 14 May '12

14 May '12

ConcurrentModificationException when LoggerContext.reset --------------------------------------------------------- Key: LBCLASSIC-318 URL: http://jira.qos.ch/browse/LBCLASSIC-318 Project: logback-classic Issue Type: Bug Affects Versions: 1.0.0 Reporter: Szczepan Faber Assignee: Logback dev list Not sure if it's a bug. Should we expect this to be thread safe: {code} //should below work in concurrent scenario? { LoggerContext context = (LoggerContext) LoggerFactory.getILoggerFactory(); //configure the context somehow context.reset() } {code} I'm facing this issue from time to time: {code} Caused by: java.util.ConcurrentModificationException at ch.qos.logback.classic.Logger.recursiveReset(Logger.java:372) at ch.qos.logback.classic.LoggerContext.reset(LoggerContext.java:223) {code} -- 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

[qos-ch/logback] ca3ec6: news about asyncappender
by Ceki Gulcu 11 May '12

11 May '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: ca3ec62535ff59dbf59deb2688e4f95088a584af https://github.com/qos-ch/logback/commit/ca3ec62535ff59dbf59deb2688e4f95088… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-11 (Fri, 11 May 2012) Changed paths: M logback-site/src/site/pages/news.html Log Message: ----------- news about asyncappender

1 0

[JIRA] Created: (LBCLASSIC-176) Asynchronous File appender
by Konstantin Alexandrov (JIRA) 11 May '12

11 May '12

Asynchronous File appender -------------------------- Key: LBCLASSIC-176 URL: http://jira.qos.ch/browse/LBCLASSIC-176 Project: logback-classic Issue Type: New Feature Components: appender Reporter: Konstantin Alexandrov Assignee: Logback dev list Attachments: AsynchRollingFileAppender.java I implement asynch rolling file appender for my application, the reason is to decrease logging time in time critical part of application. This logger save up to 2 time logging time and decrease total IO concurrency. If you found this appender usable, then please include to distribution. Thanks -- 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

5 16

[JIRA] Created: (LBGENERAL-53) Add support for SQLite in DBAppender
by Tony Trinh (JIRA) 11 May '12

11 May '12

Add support for SQLite in DBAppender ------------------------------------ Key: LBGENERAL-53 URL: http://jira.qos.ch/browse/LBGENERAL-53 Project: logback-general Issue Type: New Feature Affects Versions: unspecified Reporter: Tony Trinh Assignee: Logback dev list Priority: Minor Please add support for SQLite to DBAppender. (Patch to be attached) -- 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 3