- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-755) RollingFileAppender is not worked inside siftingAppender when using logback-access!!!
by yuanhaoliang (JIRA) 09 Oct '12

09 Oct '12

2 4

[JIRA] (LOGBACK-756) Excessive traces displayed due to AccessControlException when exception stack frames are requested
by tomsor (JIRA) 08 Oct '12

08 Oct '12

1 2

[JIRA] (LOGBACK-757) SocketAppender needs configurable timeouts
by Oliver Siegmar (JIRA) 08 Oct '12

08 Oct '12

1 0

[JIRA] (LOGBACK-747) maxHistory doesnot normally work in SizeAndTimeBasedFNATP
by Billy Wang (JIRA) 04 Oct '12

04 Oct '12

3 2

[qos-ch/logback] 4b68a6: corrected link to Shibboleth project, hash() and t...
by Ceki Gulcu 02 Oct '12

02 Oct '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 4b68a66769e09d3c00f590496705a6f308aca390 https://github.com/qos-ch/logback/commit/4b68a66769e09d3c00f590496705a6f308… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-10-02 (Tue, 02 Oct 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextVO.java M logback-site/src/site/pages/index.html Log Message: ----------- corrected link to Shibboleth project, hash() and toString methods for LoggerContextVO

1 0

[JIRA] (LOGBACK-752) Content overflow under TOC box
by Libor Jelinek (JIRA) 27 Sep '12

27 Sep '12

1 0

[JIRA] (LOGBACK-745) TimeBasedRollingPolicy does not trigger
by Tomas Jetelina (JIRA) 27 Sep '12

27 Sep '12

1 2

[JIRA] Created: (LBCORE-228) Syslog messages over 64K are discarded
by Pasi Eronen (JIRA) 25 Sep '12

25 Sep '12

Syslog messages over 64K are discarded -------------------------------------- Key: LBCORE-228 URL: http://jira.qos.ch/browse/LBCORE-228 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.30 Reporter: Pasi Eronen Assignee: Logback dev list SyslogAppenderBase truncates very long messages to 256k, which is not very useful limit, since SyslogOutputStream supports only UDP, which has maximum message size of 64k. Messages over 64k result in "java.io.IOException: Message too long" (from DatagramSocket.send, called from SyslogOutputStream.flush), but this exception is visible only in logger context status... Proposed fix: truncate long messages instead of discarding them. More specifically, change MSG_SIZE_LIMIT in SyslogAppenderBase to 65000. -- 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: (LBCLASSIC-319) SyslogAppender prints %PARSER_ERROR[nopexXXX] when suffixPattern doesn't start with [
by Markus Binsteiner (JIRA) 25 Sep '12

25 Sep '12

SyslogAppender prints %PARSER_ERROR[nopexXXX] when suffixPattern doesn't start with [ ------------------------------------------------------------------------------------- Key: LBCLASSIC-319 URL: http://jira.qos.ch/browse/LBCLASSIC-319 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.30, 1.0.0 Reporter: Markus Binsteiner Assignee: Logback dev list Priority: Minor When I use the SyslogAppender and specify a suffixPattern that starts with a whitespace or other character that is not [ logback seems to just append the string (until the first occurence of certain characters, e.g -) to the internal "%nopex" string. Subsequently it fails to parse the %nopexXXX string and prints something like: Jan 12 15:54:14 think %PARSER_ERROR[nopexXXX] [main] LogTest DEBUG FROM JAVA... to syslog. Had a look in the sourcecode, but couldn't figure out where it goes wrong, but I could confirm that if I add a whitespace to the string in this line String prefixPattern = "%syslogStart{" + facilityStr + "}%nopex "; there is no PARSER_ERROR. An additional whitespace in the logmessage though (I can live with that though). I need to be able to specify a string that doesn't start with [ though for some crazy reason (almost funny -- every other character would have been ok as far as I could figure out...). Any chance that could be looked into and included in one of the next releases? Thanks in advance... -- 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] 748b84: added setMDCPropertyMap
by Ceki Gulcu 25 Sep '12

25 Sep '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 748b8445fe8075d34b292fe1e1f364dfb3aaad03 https://github.com/qos-ch/logback/commit/748b8445fe8075d34b292fe1e1f364dfb3… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-09-25 (Tue, 25 Sep 2012) Changed paths: M logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggingEvent.java Log Message: ----------- added setMDCPropertyMap

1 0