September 2008 - logback-dev

[JIRA] Created: (LBCLASSIC-71) Failed tests: lateServerLaunch(ch.qos.logback.classic.net.SocketAppenderTest) in r1815
by Joern Huxhorn (JIRA) 29 Oct '08

29 Oct '08

Failed tests: lateServerLaunch(ch.qos.logback.classic.net.SocketAppenderTest) in r1815 -------------------------------------------------------------------------------------- Key: LBCLASSIC-71 URL: http://jira.qos.ch/browse/LBCLASSIC-71 Project: logback-classic Issue Type: Bug Environment: java version "1.6.0_07" Java(TM) SE Runtime Environment (build 1.6.0_07-b06) Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing) Maven version: 2.0.9 Java version: 1.6.0_07 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" Reporter: Joern Huxhorn Assignee: Logback dev list This test keeps failing on my system: java.lang.AssertionError: expected:<1> but was:<0> [..] at ch.qos.logback.classic.net.SocketAppenderTest.lateServerLaunch(SocketAppenderTest.java:195) Any idea why? -- 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-72) Please implement a getter for StackTraceElementProxy.ste
by Joern Huxhorn (JIRA) 29 Oct '08

29 Oct '08

Please implement a getter for StackTraceElementProxy.ste -------------------------------------------------------- Key: LBCLASSIC-72 URL: http://jira.qos.ch/browse/LBCLASSIC-72 Project: logback-classic Issue Type: Improvement Reporter: Joern Huxhorn Assignee: Logback dev list I just checked out your latest changes concerning package version information because I have to implement it for Lilith when the next version of Logback is released. At the moment StackTraceElementProxy does not have a getter for the contained StackTraceElement. It would be really helpful for me if I could access it. Otherwise I'd have to parse it from steAsString which I'd really like to prevent. I'd suggest to implement both a getter and a setter for the StackTraceElement. steAsString would need to be set to null if the STE is changed. Additionally, I'd suggest to make steAsString transient since it can be restored after deserialization. -- 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 6

[JIRA] Created: (LBCORE-54) FileAppender to support FileNamePattern option
by Chris Cheshire (JIRA) 27 Oct '08

27 Oct '08

FileAppender to support FileNamePattern option ---------------------------------------------- Key: LBCORE-54 URL: http://jira.qos.ch/browse/LBCORE-54 Project: logback-core Issue Type: Improvement Components: Appender Environment: Any Reporter: Chris Cheshire Assignee: Logback dev list It would be very useful if the base FileAppender supported the FileNamePattern option, the same as the rolling policy classes do for the RollingFileAppender. This will allow for log files to be created directly into a date based directory in the format of "logs/yyyy/MM/dd/appname.log". -- 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 6

[JIRA] Created: (LBCLASSIC-53) Add MDC Level Filtering
by Ralph Goers (JIRA) 27 Oct '08

27 Oct '08

Add MDC Level Filtering ----------------------- Key: LBCLASSIC-53 URL: http://jira.qos.ch/browse/LBCLASSIC-53 Project: logback-classic Issue Type: New Feature Environment: All Reporter: Ralph Goers Assignee: Logback dev list Attachments: MDCLevelFilter.zip The company I work for is an Application Service Provider. Requests to the same software running in a single JVM might be on behalf of any one of these companies. In addition, our middle tier contains services that my be called from several different products and are run on behalf of a user of one of these companies. Operationally, we require the ability to be able to filter based on company, product, possibly the end user or several other criteria. The TurboFilter provided allows individual values for keys in the MDC to be associated with a logging level. So if the MDC contains a key for the company the TurboFilter can be configured with the name of the company and the corresponding logging level. So if CompanyA's level is set to debug while the default level is error, only debug events for CompanyA will be passed on. -- 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 10

[JIRA] Created: (LBCORE-57) FlushableAppender
by Bruno Navert (JIRA) 27 Oct '08

27 Oct '08

FlushableAppender ----------------- Key: LBCORE-57 URL: http://jira.qos.ch/browse/LBCORE-57 Project: logback-core Issue Type: Improvement Components: Appender Affects Versions: 0.9.9 Reporter: Bruno Navert Assignee: Logback dev list Priority: Minor Attachments: FlushableAppender.java Create a FlushableAppender interface for appenders that can be manually flushed (only relevant if bufferingIO is enabled) Interface can simply extend Appender and java.io.Flushable -- 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 5

[JIRA] Created: (LBGENERAL-23) add support for package version & jar name in the stack trace
by James Strachan (JIRA) 21 Oct '08

21 Oct '08

add support for package version & jar name in the stack trace ------------------------------------------------------------- Key: LBGENERAL-23 URL: http://jira.qos.ch/browse/LBGENERAL-23 Project: logback-general Issue Type: New Feature Reporter: James Strachan Assignee: Logback dev list add support for this patch... https://issues.apache.org/bugzilla/show_bug.cgi?id=45721 -- 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: (LBCORE-56) AppenderBase getLayout returns null
by Thilo Tanner (JIRA) 20 Oct '08

20 Oct '08

AppenderBase getLayout returns null ----------------------------------- Key: LBCORE-56 URL: http://jira.qos.ch/browse/LBCORE-56 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.9 Environment: Linux Reporter: Thilo Tanner Assignee: Logback dev list Priority: Minor AppenderBase getter and setter for layout aren't abstract. Because the setter drops any value and the getter returns null, overriding the class can be very cumbersome, if you don't hav access to the source code of AppenderBase. Please make the methods abstract or introduce a layout member. -- 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 4

[JIRA] Created: (LBCORE-55) getPresentationFooter and getFileFooter are swapped
by Natan Cox (JIRA) 17 Oct '08

17 Oct '08

getPresentationFooter and getFileFooter are swapped --------------------------------------------------- Key: LBCORE-55 URL: http://jira.qos.ch/browse/LBCORE-55 Project: logback-core Issue Type: Bug Components: Appender Reporter: Natan Cox Assignee: Logback dev list If I look into the code I can see in WriterAppender writeFooter String h = layout.getFileFooter(); if ((h != null) && (this.writer != null)) { try { this.writer.write(h); String pf = layout.getPresentationFooter(); if (pf != null) { this.writer.write(pf); } And if I look into HTMLLayoutBase I see getFileFooter => </body></html> getPresentationFooter => </table> which means we are first closing the HTML and then the TABLE? Fix: String pf = layout.getPresentationFooter(); if ((pf != null) && (this.writer != null)) { try { this.writer.write(pf); String h = layout.getFileFooter(); if (h != null) { this.writer.write(h); } -- 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] Created: (LBCLASSIC-66) config file is ill-formed
by Ceki Gulcu (JIRA) 07 Oct '08

07 Oct '08

config file is ill-formed ------------------------- Key: LBCLASSIC-66 URL: http://jira.qos.ch/browse/LBCLASSIC-66 Project: logback-classic Issue Type: Sub-task Reporter: Ceki Gulcu Assignee: Ceki Gulcu -- 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: (LBCLASSIC-62) logback auto-configuration and error printing
by Ceki Gulcu (JIRA) 07 Oct '08

07 Oct '08

logback auto-configuration and error printing --------------------------------------------- Key: LBCLASSIC-62 URL: http://jira.qos.ch/browse/LBCLASSIC-62 Project: logback-classic Issue Type: Task Affects Versions: 0.9.9 Reporter: Ceki Gulcu Assignee: Ceki Gulcu Priority: Blocker Fix For: 0.9.10 Logback should make life easier for users when config files cannot be found, or they are ill-formed or when they contain errors. -- 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