- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-995) Standalone rollover gets exception
by QOS.CH (JIRA) 07 Jul '17

07 Jul '17

1 0

[JIRA] (LOGBACK-1323) Set the Logging level of the (OnConsole-)StatusListener in logback.xml
by QOS.CH (JIRA) 06 Jul '17

06 Jul '17

Tillmann Heigel created LOGBACK-1323: ---------------------------------------- Summary: Set the Logging level of the (OnConsole-)StatusListener in logback.xml Key: LOGBACK-1323 URL: https://jira.qos.ch/browse/LOGBACK-1323 Project: logback Issue Type: Improvement Components: logback-core Reporter: Tillmann Heigel Assignee: Logback dev list Priority: Minor I was looking for the possibility to set the logging level for the OnConsoleStatusListener in logback.xml. {code:java} <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener"> <level>(INFO|WARN|ERROR)</level> </statusListener> {code} @see: [https://github.com/qos-ch/logback/pull/380|https://github.com/qos-ch/logbac…] -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1322) File handles to tmp file kept open after rotation
by QOS.CH (JIRA) 04 Jul '17

04 Jul '17

Ross Ilott created LOGBACK-1322: ----------------------------------- Summary: File handles to tmp file kept open after rotation Key: LOGBACK-1322 URL: https://jira.qos.ch/browse/LOGBACK-1322 Project: logback Issue Type: Bug Affects Versions: 1.2.3 Environment:        <configuration> <appender name="stdout" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d\{HH:mm:ss.SSS} [%thread] %-5level [%file:%line] - %msg%n</pattern> </encoder> </appender> <appender name="logfile" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>log/kairosdb.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>/var/log/kairosdb/kairosdb.%d.%i.log.gz</fileNamePattern>  <maxHistory>30</maxHistory>  <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>100MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy>  <cleanHistoryOnStart>true</cleanHistoryOnStart> </rollingPolicy> <encoder> <pattern>%d\{MM-dd|HH:mm:ss.SSS} [%thread] %-5level [%file:%line] - %msg%n</pattern> </encoder> </appender> <logger name="com.mchange.v2.c3p0" level="WARN"/>    <root level="INFO"> <appender-ref ref="stdout"/> <appender-ref ref="logfile"/> </root> </configuration> Reporter: Ross Ilott Assignee: Logback dev list I'm using kairosdb 1.1.3 which uses logback as it's logging library. When the log reaches 100MB the log rotates successfully, but many .tmp files are held open, resulting in the disk space not being freed up: {{java 13075 31552 root 2w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31561 root 1w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31561 root 2w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31632 root 1w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31632 root 2w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31637 root 1w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31637 root 2w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31639 root 1w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted) java 13075 31639 root 2w REG 253,1 104911776 589454 /opt/kairosdb/log/kairosdb.log1696340173764370.tmp (deleted)}} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1321) SMTPAppender only send ERROR Level log
by QOS.CH (JIRA) 03 Jul '17

03 Jul '17

Backer created LOGBACK-1321: ------------------------------- Summary: SMTPAppender only send ERROR Level log Key: LOGBACK-1321 URL: https://jira.qos.ch/browse/LOGBACK-1321 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.3 Environment: Jdk 1.8 Reporter: Backer Assignee: Logback dev list <appender name="EMAILDEV" class="ch.qos.logback.classic.net.SMTPAppender"> <smtpHost>$\{smtpHost}</smtpHost> <smtpPort>$\{smtpPort}</smtpPort> <username>$\{username}</username> <password>$\{password}</password> <SSL>$\{SSL}</SSL> <asynchronousSending>false</asynchronousSending> <to>$\{email_to_dev}</to> <from>$\{email_from}</from> <subject>$\{email_subject_dev}</subject> <layout class="ch.qos.logback.classic.html.HTMLLayout" > <pattern>%d\{yyyy-MM-dd HH:mm:ss.SSS}[%thread] %-5level %logger\{50} - %msg%n</pattern> </layout>  <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTracker">  <bufferSize>1</bufferSize> </cyclicBufferTracker> </appender> logger.warn("TEst"); -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1320) Logback not capturing all log messages from JUL
by QOS.CH (JIRA) 28 Jun '17

28 Jun '17

Nathan Lighthart created LOGBACK-1320: ----------------------------------------- Summary: Logback not capturing all log messages from JUL Key: LOGBACK-1320 URL: https://jira.qos.ch/browse/LOGBACK-1320 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.3, 0.9.25 Reporter: Nathan Lighthart Assignee: Logback dev list Priority: Minor Attachments: JULHelper.java, logback.xml, Main.java INFO and CONFIG messages in JUL are classified as INFO messages in Logback. FINE and FINER messages in JUL are classified as DEBUG messages in Logback. When using the LevelChangePropagator, it is expected when the Logback level is INFO that both INFO and CONFIG messages in JUL are captured. The same should be true about FINE and FINER messages when the Logback level is DEBUG. However, when the Logback level is INFO, CONFIG messages are not captured; while, INFO messages are. When the Logback level is DEBUG, FINER messages are not captured; while, FINE messages are. How to Reproduce: I have attached my logback configuration file as well as a simple main class which logs INFO, CONFIG, FINE, FINER, and FINEST messages. Solutions: It appears the problem stems from JULHelper.asJULLevel() method. When the level is DEBUG, FINE is returned. When the level is INFO, then INFO is returned. This method should return FINER for DEBUG and CONFIG for INFO. I have attached a modified version of the JULHelper. As JULHelper.asJULLevel() is part of the public API this change may impact users that directly call this method. Therefore if you want to preserve backwards compatibility, you can add another method like asLowerJULLevel() which returns FINER and CONFIG in the appropriate place. Then in the LevelChangePropagator call asLowerJULLevel() in the propagate() method. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1319) framework packages are not excluded properly
by QOS.CH (JIRA) 24 Jun '17

24 Jun '17

Bug Reporter created LOGBACK-1319: ------------------------------------- Summary: framework packages are not excluded properly Key: LOGBACK-1319 URL: https://jira.qos.ch/browse/LOGBACK-1319 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.3 Reporter: Bug Reporter Assignee: Logback dev list The [LoggerContext.getFrameworkPackages|https://logback.qos.ch/apidocs/ch/qos/logback/classic/LoggerContext.html#getFrameworkPackages()] documentation says this is a list of packages (including their subpackages) that get excluded when tracing the caller. But the implementation in [CallerData.isInFrameworkSpaceList|https://github.com/qos-ch/logback/blob/ma…] is wrong because "com.foo" matches "com.foobar" which is not its subpackage. I suggest changing {code:java} if (currentClass.startsWith(s)){code} to {code:java} if (currentClass.startsWith(s + ".")){code} or even {code:java} if (currentClass.equals(s) || currentClass.startsWith(s + ".")){code} in case someone relies on this behavior to exclude specific classes (which would be nice anyway). We could also add {code:java} if (s.equals("")) return !currentClass.contains("."){code} to support excluding the default package classes. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1318) LoggingEvent.prepareForDeferredProcessing doesn't need to call LoggingEvent.getFormattedMessage
by QOS.CH (JIRA) 23 Jun '17

23 Jun '17

William Li created LOGBACK-1318: ----------------------------------- Summary: LoggingEvent.prepareForDeferredProcessing doesn't need to call LoggingEvent.getFormattedMessage Key: LOGBACK-1318 URL: https://jira.qos.ch/browse/LOGBACK-1318 Project: logback Issue Type: Improvement Components: logback-classic Reporter: William Li Assignee: Logback dev list Priority: Minor LoggingEvent.prepareForDeferredProcessing should be called when using asynchronous or deferred logging. The code is as blow. The first line may cause log event serialization, which is time-cosuming when the message is big. Actually, it is not need to have this line of code. The code was added in [https://github.com/qos-ch/logback/commit/dfd340815e36f475cd014fd85915dbbafa….] by Ceki Gulcu in 2010. The comment is "all logback-classic and logback-core tests pass". Actually, no test case failure if this line is removed. I would suggest to remove this line, so that the log event will not be serialized untile the logger thread really need the formatted message. {quote}public void prepareForDeferredProcessing() \{ _*this.getFormattedMessage();*_ this.getThreadName(); // fixes http://jira.qos.ch/browse/LBCLASSIC-104 this.getMDCPropertyMap(); }{quote} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1317) Change the scope of the servlet-api from compile/optional to provided
by QOS.CH (JIRA) 23 Jun '17

23 Jun '17

1 0

[JIRA] (LOGBACK-1317) Change the scope of the servlet-api from compile/optional to provided
by QOS.CH (JIRA) 23 Jun '17

23 Jun '17

Emmanuel Bourg created LOGBACK-1317: --------------------------------------- Summary: Change the scope of the servlet-api from compile/optional to provided Key: LOGBACK-1317 URL: https://jira.qos.ch/browse/LOGBACK-1317 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.2.3 Reporter: Emmanuel Bourg Assignee: Logback dev list Priority: Trivial The dependency for the Servlet API has the {{compile}} scope and is marked as optional. Usually in this situation the {{provided}} scope should be used because it's supposed to be provided by the servlet container. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1316) Docs for reqParameter describe it as "Parameter of the response"
by QOS.CH (JIRA) 22 Jun '17

22 Jun '17

Robert Kuhar created LOGBACK-1316: ------------------------------------- Summary: Docs for reqParameter describe it as "Parameter of the response" Key: LOGBACK-1316 URL: https://jira.qos.ch/browse/LOGBACK-1316 Project: logback Issue Type: Bug Components: logback-access Environment: Reporter: Robert Kuhar Assignee: Logback dev list Priority: Minor I'm looking at [https://logback.qos.ch/manual/layouts.html#AccessPatternLayout] and see that there is a parameter who's "Conversion Word" is reqParameter but who's "Effect" is described as "Parameter of the response". Later in the "Effect" its says "...looks for the corresponding parameter in the request.". That first sentence of the Effect should be "Parameter of the request.", no? -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0