- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-796) RollingFileAppender should throw exception when File matches FileNamePattern
by The Alchemist (JIRA) 09 Jan '13

09 Jan '13

1 1

[qos-ch/logback-contrib] a887f3: All jars are now also OSGi bundles.
by Christian Trutz 08 Jan '13

08 Jan '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: a887f3f462da3847bae466d981c4ab469a15d080 https://github.com/qos-ch/logback-contrib/commit/a887f3f462da3847bae466d981… Author: Christian Trutz <christian.trutz(a)belaso.de> Date: 2013-01-08 (Tue, 08 Jan 2013) Changed paths: M pom.xml Log Message: ----------- All jars are now also OSGi bundles. Signed-off-by: Christian Trutz <christian.trutz(a)belaso.de>

1 0

[JIRA] (LOGBACK-781) ch.qos.logback.classic.LoggerContext.getLogger() is hard to understand; can be shortend with a little recursion
by David Tonhofer (JIRA) 08 Jan '13

08 Jan '13

1 1

[JIRA] (LOGBACK-795) Logback spawning threads in AsynchronousCompressor
by KOVACS Istvan (JIRA) 08 Jan '13

08 Jan '13

1 0

[JIRA] Created: (LBCLASSIC-249) Logging Exceptions using DBAppender fails (at least on Oracle), when message or stack frame is longer than 254 bytes
by Andreas Zielke (JIRA) 07 Jan '13

07 Jan '13

Logging Exceptions using DBAppender fails (at least on Oracle), when message or stack frame is longer than 254 bytes -------------------------------------------------------------------------------------------------------------------- Key: LBCLASSIC-249 URL: http://jira.qos.ch/browse/LBCLASSIC-249 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.28 Environment: Oracle DBMS Reporter: Andreas Zielke Assignee: Logback dev list Priority: Minor Sometimes the DBAppender failed to log Exceptions, so I checked the status of the StatusManager and found the folloging problem: java.sql.BatchUpdateException: ORA-12899: Wert zu groß für Spalte "SUBSYSTEMTEST"."LOGGING_EVENT_EXCEPTION"."TRACE_LINE" (aktuell: 692, maximal: 254) Possible fix: After reading the code of DBAppender I subclassed it and changed the code of the method void updateExceptionStatement(PreparedStatement exceptionStatement, String txt, short i, long eventId) so that the text would be shortened accordingly. This seems to be the most consistent workaround, as many other columns are also only 254 bytes wide. I'd much rather have a wider column and not loose information, though. (This would be consistent with the changes to LOGGING_EVENT_EXCEPTION as proposed in LBCLASSIC-170). -- 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 3

[JIRA] (LOGBACK-793) Logback RollingFileAppender error when trying to do manual rollover
by Razvan Jurca (JIRA) 04 Jan '13

04 Jan '13

1 0

[JIRA] (LOGBACK-792) Column size to big for database columns used by DBAppender
by Alexander Gerbig (JIRA) 03 Jan '13

03 Jan '13

1 0

[JIRA] (LOGBACK-791) Design issue: Should an OnConsoleStatusListener be addable to the StatusManager if there already is one?
by David Tonhofer (JIRA) 02 Jan '13

02 Jan '13

1 2

[JIRA] (LOGBACK-790) Static code analysis reveals not fully covered enum in ch.qos.logback.core.joran.util.PropertySetter
by David Tonhofer (JIRA) 01 Jan '13

01 Jan '13

1 1

[JIRA] (LOGBACK-789) Static code analysis reveals not fully covered enum in ch.qos.logback.core.subst.Tokenizer
by David Tonhofer (JIRA) 01 Jan '13

01 Jan '13

1 0