February 2010 - logback-dev

[JIRA] Created: (LBSITE-36) Example 7.5 Is Not Thread-Safe
by john jimenez (JIRA) 18 Mar '10

18 Mar '10

Example 7.5 Is Not Thread-Safe ------------------------------ Key: LBSITE-36 URL: http://jira.qos.ch/browse/LBSITE-36 Project: logback-site Issue Type: Bug Components: Documentation Affects Versions: unspecified Reporter: john jimenez Assignee: Logback dev list Example 7.5 in http://logback.qos.ch/manual/mdc.html is not thread-safe because userRegistered is declared as a global variable. -- 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 5

[JIRA] Created: (LBCORE-93) FlushingPolicy
by Ceki Gulcu (JIRA) 18 Mar '10

18 Mar '10

FlushingPolicy -------------- Key: LBCORE-93 URL: http://jira.qos.ch/browse/LBCORE-93 Project: logback-core Issue Type: New Feature Reporter: Ceki Gulcu Assignee: Logback dev list Let flushing be a settable policy of WriteAppender. Thus, the user would be able to set the FlushingPolicy of a WriterAppender or any derived class which would allow you to flush the underlying output stream according to any criteria available to the shouldFlush() method (see below), including time. Here is the relevant interface: interface FlushingPolicy { booelan shouldFlush(LoggingEvent e); } We could easily imagine a policy flushing on every warning or error in addition to special markers. For example, Marker FLUSH = MarkerFactory.getMarker("FLUSH"); logger.info(FLUSH, "finished serving request {}", request.getId()); -- 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-169) Customizing table names used by DbAppender
by Tomasz Nurkiewicz (JIRA) 10 Mar '10

10 Mar '10

Customizing table names used by DbAppender ------------------------------------------ Key: LBCLASSIC-169 URL: http://jira.qos.ch/browse/LBCLASSIC-169 Project: logback-classic Issue Type: Improvement Components: appender Affects Versions: 0.9.18 Reporter: Tomasz Nurkiewicz Assignee: Logback dev list Priority: Minor ch.qos.logback.classic.db.DBAppender uses hard-coded table names for logging events: logging_event, logging_event_property and logging_event_exception. Allowing to change these default names has two benefits: * There are systems where database table names must follow some naming conventions (prefixes, using underscores vs. camel case) * One could create several Db appenders, each operating on different set of tables (for performance reasons or more fine grained logging and filtering) Each table name would be configured using a property in logback.xml. Default values for table names would be the same as present ones to maintain backward compatibility. If you are interested in this feature let me know, I can implement it and provide a patch. -- 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

5 16

[JIRA] Created: (LBCORE-113) SMTPAppender should have support for avoiding flooding
by Ceki Gulcu (JIRA) 03 Mar '10

03 Mar '10

SMTPAppender should have support for avoiding flooding ------------------------------------------------------ Key: LBCORE-113 URL: http://jira.qos.ch/browse/LBCORE-113 Project: logback-core Issue Type: New Feature Reporter: Ceki Gulcu Assignee: Logback dev list -- 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: (LBCORE-133) Writing subsequent to an IO failure
by Ceki Gulcu (JIRA) 03 Mar '10

03 Mar '10

Writing subsequent to an IO failure ----------------------------------- Key: LBCORE-133 URL: http://jira.qos.ch/browse/LBCORE-133 Project: logback-core Issue Type: Sub-task Components: Appender Affects Versions: 0.9.18 Reporter: Ceki Gulcu Assignee: Logback dev list See http://www.qos.ch/pipermail/logback-user/2009-December/001382.html -- 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: (LBCORE-109) FileAppender writing to a shared (networked) file system
by Ceki Gulcu (JIRA) 03 Mar '10

03 Mar '10

FileAppender writing to a shared (networked) file system -------------------------------------------------------- Key: LBCORE-109 URL: http://jira.qos.ch/browse/LBCORE-109 Project: logback-core Issue Type: Bug Affects Versions: 0.9.9, 0.9.10, 0.9.11, 0.9.12, 0.9.13, 0.9.14, 0.9.15 Reporter: Ceki Gulcu Assignee: Logback dev list FileAppender writing to a shared (networked) file system with lost networked connection. -- 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: (LBCLASSIC-112) ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest hangs on Mac OS X
by Joern Huxhorn (JIRA) 03 Mar '10

03 Mar '10

ch.qos.logback.classic.net.SMTPAppender_SubethaSMTPTest hangs on Mac OS X ------------------------------------------------------------------------- Key: LBCLASSIC-112 URL: http://jira.qos.ch/browse/LBCLASSIC-112 Project: logback-classic Issue Type: Bug Affects Versions: 0.9.16 Reporter: Joern Huxhorn Assignee: Logback dev list This test keeps hanging repeatedly at the very same spot. I'll attach a file with further info. -- 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 10

Better introspection into logging setup
by Durchholz, Joachim 01 Mar '10

01 Mar '10

Taken here from Bugzilla #169 on Ceki's request. Reworded to improve presentation. Within the SLF4J framework, I'd like to - have a way to enumerate all active loggers, and find out at what logging levels they are, and - get an event whenever the set of active loggers or their configuration changes. The use case is this: I need to integrate multiple libraries, each using a different logging framework. Some of them use java.util.logging, and since j.u.l. does not respond directly to the SLF4J configuration, I currently need to keep two sets of configurations, one for SLF4J loggers and one for j.u.l. (I could have the bridge run with maximum logging and let the SLF4J side sort out which messages are needed and which aren't, but that's killing performance.) Design considerations (i.e. that's how far I got): So I thought I'd hack something for the j.u.l. bridge to mimick the SLF4J loggers. E.g. iterate over all SLF4J loggers and install a corresponding j.u.l logger, instead of installing a root logger and logging everything. Turns out LoggerFactory does not return a list of active loggers :( The other thought that occurred to me what as SLF4J-managed loggers are reconfigured at runtime, they should inform the j.u.l. brigde so it can reconfigure the j.u.l. side as well. Feedback welcome. Regards, Jo

1 1

[JIRA] Created: (LBCORE-129) IncludeActionTest fails at unknownURL()
by Joern Huxhorn (JIRA) 27 Feb '10

27 Feb '10

IncludeActionTest fails at unknownURL() --------------------------------------- Key: LBCORE-129 URL: http://jira.qos.ch/browse/LBCORE-129 Project: logback-core Issue Type: Bug Affects Versions: 0.9.18 Environment: Mac OS X 10.5.8 Reporter: Joern Huxhorn Assignee: Logback dev list Instead of an UnknownHostException the actual exception is java.io.IOException: Server returned HTTP response code: 503 for URL: http://logback2345.qos.ch -- 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 2

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, encoder, updated. v0.9.18-50-g8381bae
by git-noreply＠pixie.qos.ch 27 Feb '10

27 Feb '10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, encoder has been updated via 8381bae9d2899def5d9a9420edd2d53811ddba5b (commit) from 4577cf0a7f55e1162d72691951476d9ae876f0f1 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=8381bae9d2899def5d9a9420… http://github.com/ceki/logback/commit/8381bae9d2899def5d9a9420edd2d53811ddb… commit 8381bae9d2899def5d9a9420edd2d53811ddba5b Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat Feb 27 10:37:22 2010 +0100 Skip the UnknownHostException on Mac. This fixes LBCORE-129 diff --git a/logback-core/src/test/java/ch/qos/logback/core/joran/action/IncludeActionTest.java b/logback-core/src/test/java/ch/qos/logback/core/joran/action/IncludeActionTest.java index d7d621c..d242e9f 100644 --- a/logback-core/src/test/java/ch/qos/logback/core/joran/action/IncludeActionTest.java +++ b/logback-core/src/test/java/ch/qos/logback/core/joran/action/IncludeActionTest.java @@ -38,6 +38,7 @@ import ch.qos.logback.core.joran.spi.JoranException; import ch.qos.logback.core.joran.spi.Pattern; import ch.qos.logback.core.status.Status; import ch.qos.logback.core.status.StatusChecker; +import ch.qos.logback.core.testUtil.Env; import ch.qos.logback.core.testUtil.RandomUtil; import ch.qos.logback.core.util.CoreTestConstants; import ch.qos.logback.core.util.StatusPrinter; @@ -75,7 +76,7 @@ public class IncludeActionTest { static final String INCLUDED_AS_RESOURCE = "asResource/joran/inclusion/includedAsResource.xml"; int diff = RandomUtil.getPositiveInt(); - + public IncludeActionTest() { HashMap<Pattern, Action> rulesMap = new HashMap<Pattern, Action>(); rulesMap.put(new Pattern("x"), new NOPAction()); @@ -145,22 +146,22 @@ public class IncludeActionTest { File f = new File(tmpOut); assertTrue(f.exists()); assertTrue(f.delete()); - + } - String copyToTemp(String in) throws IOException { + String copyToTemp(String in) throws IOException { FileInputStream fis = new FileInputStream(in); - String out = CoreTestConstants.OUTPUT_DIR_PREFIX+"out"+diff; + String out = CoreTestConstants.OUTPUT_DIR_PREFIX + "out" + diff; FileOutputStream fos = new FileOutputStream(out); int b; - while((b=fis.read()) != -1) { + while ((b = fis.read()) != -1) { fos.write(b); } fis.close(); fos.close(); return out; } - + @Test public void malformedURL() throws JoranException { System.setProperty(INCLUDE_KEY, "htp://logback.qos.ch"); @@ -176,7 +177,11 @@ public class IncludeActionTest { tc.doConfigure(TOP_BY_URL); assertEquals(Status.ERROR, context.getStatusManager().getLevel()); StatusChecker sc = new StatusChecker(context.getStatusManager()); - assertTrue(sc.containsException(UnknownHostException.class)); + // OS X throws IOException instead of UnknownHostException + // http://jira.qos.ch/browse/LBCORE-129 + if (!Env.isMac()) { + assertTrue(sc.containsException(UnknownHostException.class)); + } } @Test ----------------------------------------------------------------------- Summary of changes: .../core/joran/action/IncludeActionTest.java | 19 ++++++++++++------- 1 files changed, 12 insertions(+), 7 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0