December 2009 - logback-dev

[JIRA] Created: (LBCORE-113) SMTPAppender should have support for avoiding flooding
by Ceki Gulcu (JIRA) 03 Mar '10

03 Mar '10

SMTPAppender should have support for avoiding flooding ------------------------------------------------------ Key: LBCORE-113 URL: http://jira.qos.ch/browse/LBCORE-113 Project: logback-core Issue Type: New Feature Reporter: Ceki Gulcu Assignee: Logback dev list -- 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

1 1

[JIRA] Created: (LBCORE-109) FileAppender writing to a shared (networked) file system
by Ceki Gulcu (JIRA) 03 Mar '10

03 Mar '10

FileAppender writing to a shared (networked) file system -------------------------------------------------------- Key: LBCORE-109 URL: http://jira.qos.ch/browse/LBCORE-109 Project: logback-core Issue Type: Bug Affects Versions: 0.9.9, 0.9.10, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15 Reporter: Ceki Gulcu Assignee: Logback dev list FileAppender writing to a shared (networked) file system with lost networked connection. -- 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 7

[JIRA] Created: (LBCLASSIC-112) ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest hangs on Mac OS X
by Joern Huxhorn (JIRA) 03 Mar '10

03 Mar '10

ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest hangs on Mac OS X ------------------------------------------------------------------------- Key: LBCLASSIC-112 URL: http://jira.qos.ch/browse/LBCLASSIC-112 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.16 Reporter: Joern Huxhorn Assignee: Logback dev list This test keeps hanging repeatedly at the very same spot. I'll attach a file with further info. -- 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 10

[JIRA] Created: (LBCORE-129) IncludeActionTest fails at unknownURL()
by Joern Huxhorn (JIRA) 27 Feb '10

27 Feb '10

IncludeActionTest fails at unknownURL() --------------------------------------- Key: LBCORE-129 URL: http://jira.qos.ch/browse/LBCORE-129 Project: logback-core Issue Type: Bug Affects Versions: 0.9.18 Environment: Mac OS X 10.5.8 Reporter: Joern Huxhorn Assignee: Logback dev list Instead of an UnknownHostException the actual exception is java.io.IOException: Server returned HTTP response code: 503 for URL: http://logback2345.qos.ch -- 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 2

[JIRA] Created: (LBCORE-130) Can't use path with parenthesis for logging
by Matthias (JIRA) 10 Feb '10

10 Feb '10

Can't use path with parenthesis for logging ------------------------------------------- Key: LBCORE-130 URL: http://jira.qos.ch/browse/LBCORE-130 Project: logback-core Issue Type: Bug Components: Pattern Affects Versions: 0.9.16 Reporter: Matthias Assignee: Logback dev list Priority: Minor I configured following appender: <appender name="WS_LOG" class="ch.qos.logback.core.rolling.RollingFileAppender"> <Encoding>UTF-8</Encoding> <File>${catalina.home}/logs/webserver.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${catalina.home}/logs/webserver.%d{yyyy-MM-dd}.log</FileNamePattern> <MaxHistory>14</MaxHistory> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <PresentationHeader>ARCHIKART Webserver Logs</PresentationHeader> <Pattern>%date{dd.MM HH:mm:ss} %-20.20(%level [%thread]) - %msg%n</Pattern> </layout> </appender> In this case ${catalina.home} is "C:\Program Files (x86)\webserver". When the logback.xml is parsed the path "C:\\Program Files (x86)\\webserver\\/logs/webserver.%d{yyyy-MM-dd}.log" is only parsed to "C:\\Program Files (x86". That's why it causes an exception "FileNamePattern ... does not contain a valid DateToken" in TimeBasedRollingPolicy. When I use a path without parenthesis logging works fine. But this is the default program files directory on windows vista 64bit. I did not test 0.9.18, because I thought it would be a bigger work to change the logging of the server. I did not read anything of this in the Jira, so I think this error might still exist. -- 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

RFC 5424 and Structured Data support.
by Ralph Goers 29 Jan '10

29 Jan '10

I would appreciate it if you would review git://github.com/rgoers/logback.git and git://github.com/rgoers/slf4j.git and incorporate that into the "official" logback source. The forks include fixes for LBCLASSIC-116, LBCLASSIC-154, possibly LBCLASSIC-153. The SLF4J changes include support LBCLASSIC-116 by way of fixing SLF4J bug 148 and also includes fixes for SLF4J bugs 31 and 127. Both of my forks include all of the latest changes in your forks. Ralph

6 29

logback async appender
by Gordon Sims 02 Jan '10

02 Jan '10

We recently switched several applications from log4j to logback and were wondering about the lack of async appender in logback. Is it not needed? I thought it was a good thing for performance and reliability reasons. I see there is an old enhancement request for it in logback bugzilla, http://bugzilla.qos.ch/show_bug.cgi?id=55 It seems that someone attempted this earlier this year (but maybe hasn't checked in yet?) http://old.nabble.com/how-to-get-appender-ref-list-via-Joran-to22295581.htm… If needed and desired, we could work on a patch for this feature. In general, should it work similar to the log4j one? Or is someone else already working on it? thanks, -Gordon

3 3

[JIRA] Created: (LBCLASSIC-175) ILoggingEvent prepareForDeferredProcessing does not include callerDataArray
by Konstantin Alexandrov (JIRA) 02 Jan '10

02 Jan '10

ILoggingEvent prepareForDeferredProcessing does not include callerDataArray --------------------------------------------------------------------------- Key: LBCLASSIC-175 URL: http://jira.qos.ch/browse/LBCLASSIC-175 Project: logback-classic Issue Type: Bug Components: layout Reporter: Konstantin Alexandrov Assignee: Logback dev list I've implement asynchronous file appender, and enqueue events, but %caller pattern can not be used in the case of deferred processing becouse caller information is losed. My suggestion is to create Throwable object in prepareForDeferredProcessing -- 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 7

[JIRA] Created: (LBCLASSIC-172) Use WeakHashMap instead of Hashtable in LoggerContext
by Joern Huxhorn (JIRA) 15 Dec '09

15 Dec '09

Use WeakHashMap instead of Hashtable in LoggerContext ----------------------------------------------------- Key: LBCLASSIC-172 URL: http://jira.qos.ch/browse/LBCLASSIC-172 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.9.18 Reporter: Joern Huxhorn Assignee: Logback dev list Preventing garbage-collection of unused Loggers is a bad idea. The following code should not fail: for(int i=0;i<10000000;i++) { LoggerFactory.getLogger("Foo."+i).debug("Foo!"); } -- 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 17

[JIRA] Created: (LBCLASSIC-102) Suggestion: Change logger name of inner classes.
by Joern Huxhorn (JIRA) 15 Dec '09

15 Dec '09

Suggestion: Change logger name of inner classes. ------------------------------------------------ Key: LBCLASSIC-102 URL: http://jira.qos.ch/browse/LBCLASSIC-102 Project: logback-classic Issue Type: Improvement Components: appender Affects Versions: 0.9.15 Reporter: Joern Huxhorn Assignee: Logback dev list At the moment, the logger name of inner classes is OuterClass$InnerClass. Because of that, the logging level of OuterClass isn't inherited by InnerClass at the moment. If LoggerFactory changed the logger name to OuterClass.InnerClass instead, InnerClass would inherit the logging level of OuterClass which seems intuitively correct. I'd suggest to accept both $InnerClass and .InnerClass style in logback configurations for compatibility and usability reasons. -- 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

4 14