April 2007 - logback-dev - mailman3.qos.ch

[Bug 55] New: Implement AsyncAppender
by bugzilla-daemon＠pixie.qos.ch 22 Apr '08

22 Apr '08

http://bugzilla.qos.ch/show_bug.cgi?id=55 Summary: Implement AsyncAppender Product: logback-classic Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: enhancement Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: anders_wallgren(a)alum.mit.edu Being able to write log files in the background is a requirement for production deployments of anything we would write on top of logback. Bonus points for including a feature to periodically flush the output. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

[Bug 52] New: Unable to use <onMatch> in logback.xml
by bugzilla-daemon＠pixie.qos.ch 19 Mar '08

19 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=52 Summary: Unable to use <onMatch> in logback.xml Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: kenichi-qos(a)sysart.jp With logback-0.9.2, when logback.xml contains <onMatch> or <onMismatch> tag, the following error occurs: ERROR in ch.qos.logback.core.joran.spi.Interpreter@30ae41 - no applicable action for [onMatch], current pattern is [[configuration][appender][filter][onMatch]] ERROR in ch.qos.logback.core.joran.spi.Interpreter@30ae41 - no applicable action for [onMismatch], current pattern is [[configuration][appender][filter][onMismatch]] Since I can specify neither <onMatch> nor <onMismatch>, I am unable to make use of EvaluatorFilter, which is one of the reasons I'm considering to use logback over log4j. The cause of the problem is the two methods which have been added to ch.qos.logback.core.filter.AbstractMatcherFilter (Revision 1380): http://svn.qos.ch/viewvc/logback/trunk/logback-core/src/main/java/ch/qos/lo… Because the return type of the getter method differs from the parameter type of the setter method, java.beans.PropertyDescriptor for the properties (onMatch and onMismatch) obtained in ch.qos.logback.core.util.PropertySetter contain no writeMethod (null value, confirmed with jdb-1.6), making PropertySetter.canContainComponent return NOT_FOUND. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 3

[Bug 8] New: The insertion of a percent symbol causes the Parser to crash
by bugzilla-daemon＠pixie.qos.ch 19 Mar '08

19 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=8 Summary: The insertion of a percent symbol causes the Parser to crash Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Pattern AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch When inserting the percent char twice, so that it appears in the PatternLayout output, a number format exception is thrown. It does not prevent from using normally the PatternLayout. trace: ERROR in ch.qos.logback.core.joran.spi.Interpreter@131f71a - Exception in Action for tag <layout>8:14 java.lang.NumberFormatException: For input string: "% %" java.lang.NumberFormatException: For input string: "% %" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:447) at java.lang.Integer.parseInt(Integer.java:497) at ch.qos.logback.core.pattern.FormatInfo.valueOf(FormatInfo.java:70) at ch.qos.logback.core.pattern.parser.Parser.T(Parser.java:84) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:51) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.parse(Parser.java:31) at ch.qos.logback.core.pattern.PatternLayoutBase.start(PatternLayoutBase.java:76) at ch.qos.logback.core.joran.action.AbstractLayoutAction.end(AbstractLayoutAction.java:75) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:289) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:152) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:125) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:101) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:84) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:77) at mainPackage.ConfigTester.main(ConfigTester.java:21) -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 5

[Bug 64] New: Logback MDC context is not inherited by child threads.
by bugzilla-daemon＠pixie.qos.ch 04 Mar '08

04 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=64 Summary: Logback MDC context is not inherited by child threads. Product: logback-classic Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: bendis(a)bendis.cz As stated in the javadoc documentation, the ch.qos.logback.classic.MDC should be inherited by a child thread: "A child thread automatically inherits a copy of the mapped diagnostic context of its parent." But the context is NOT ihnerited by child threads - the context HashMap is stored in the ThreadLocal, not in the InheritableThreadLocal. Regards, Bendis -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

[Bug 57] New: Problems getting autogenerated Keys in Oracle with Oracle JDBC 10.2.03
by bugzilla-daemon＠pixie.qos.ch 11 Jan '08

11 Jan '08

http://bugzilla.qos.ch/show_bug.cgi?id=57 Summary: Problems getting autogenerated Keys in Oracle with Oracle JDBC 10.2.03 Product: logback-core Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: critical Priority: P1 Component: Appender AssignedTo: logback-dev(a)qos.ch ReportedBy: klaus(a)ungers-online.com I've encountered troubles logging StackTrace/MDC entries with die DBAppender on our plattform! We are using Oracle 9.2.0.6.0 on a Solaris Box with Oracle JDBC Driver 10.2.0.3! I've debugged the processing of LogMessages into DBAppenderBase.append()! There I found a call "con.prepareStatement(getInsertSQL())" which is followed by a call "subAppend(...)" As far as I understand Oracle Drivers return generatedKeys only, if you use the right prepareStatement() methods, which is in my understanding the following: PreparedStatement prepareStatement(String sql, int autoGeneratedKeys) throws SQLException @see http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Connection.html#prepareSta… which is available since JDK 1.4 -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 4

[Bug 67] New: feature request: XMLLayout (cfr. log4j)
by bugzilla-daemon＠pixie.qos.ch 25 Nov '07

25 Nov '07

http://bugzilla.qos.ch/show_bug.cgi?id=67 Summary: feature request: XMLLayout (cfr. log4j) Product: logback-classic Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: dirk(a)onesparrow.com see Summary -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 1

[Bug 69] New: I18N Patch
by bugzilla-daemon＠pixie.qos.ch 18 Nov '07

18 Nov '07

http://bugzilla.qos.ch/show_bug.cgi?id=69 Summary: I18N Patch Product: Console Plugin Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: interface AssignedTo: logback-dev(a)qos.ch ReportedBy: sdavids(a)gmx.de -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 6

[Bug 56] New: Improve filters
by bugzilla-daemon＠pixie.qos.ch 22 Aug '07

22 Aug '07

http://bugzilla.qos.ch/show_bug.cgi?id=56 Summary: Improve filters Product: Console Plugin Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: enhancement Priority: P1 Component: interface AssignedTo: logback-dev(a)qos.ch ReportedBy: xavier.hanin(a)gmail.com On my wish list for the plugin, more customizable filters: * having two kind of filters, the current one, and in memory one, so that the filter could be applied to already logged events, as the pattern. * being able to configure filters per project. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

[Bug 38] New: Display a message when used behind slf4j
by bugzilla-daemon＠pixie.qos.ch 21 Aug '07

21 Aug '07

http://bugzilla.qos.ch/show_bug.cgi?id=38 Summary: Display a message when used behind slf4j Product: logback-general Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: build-structure AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch Logback should display a message when it is used as SLF4J's implementation. We should find a way to tell the user that it's logback that is being used, without polluting any output. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 1

[Bug 39] New: Introduce concept of MDC as soon ass they are referenced
by bugzilla-daemon＠pixie.qos.ch 21 Aug '07

21 Aug '07

http://bugzilla.qos.ch/show_bug.cgi?id=39 Summary: Introduce concept of MDC as soon ass they are referenced Product: logback-site Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: normal Priority: P3 Component: Documentation AssignedTo: logback-dev(a)qos.ch ReportedBy: xavier.hanin(a)gmail.com While reading the documentation I had the feeling that MDC was introduced too late. Indeed, you reference MDC the first time in chapter 2 (as far as I can say), without giving even an hint on what it is. Several other chapters reference this concept, but it's only in chapter 7 that I understood what it is. Maybe adding a short introduction to this concept (and the concept of Marker) in chapter 2 would help the reader? -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2