- slf4j-dev - mailman3.qos.ch

[qos-ch/slf4j] 95b5ef: fix for bug 264
by Matt Bishop 26 Sep '14

26 Sep '14

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: 95b5efdd112278c604e9f61afc85c309401f3dc8 https://github.com/qos-ch/slf4j/commit/95b5efdd112278c604e9f61afc85c309401f… Author: justdoo <justdooh(a)gmail.com> Date: 2012-03-30 (Fri, 30 Mar 2012) Changed paths: M slf4j-api/src/main/java/org/slf4j/helpers/MessageFormatter.java M slf4j-jdk14/src/main/java/org/slf4j/impl/JDK14LoggerAdapter.java M slf4j-log4j12/src/main/java/org/slf4j/impl/Log4jLoggerAdapter.java Log Message: ----------- fix for bug 264 Commit: 0d3b1537b1575f92776c70635085c3f2d9567a63 https://github.com/qos-ch/slf4j/commit/0d3b1537b1575f92776c70635085c3f2d956… Author: Matt Bishop <matt(a)thebishops.org> Date: 2014-09-26 (Fri, 26 Sep 2014) Changed paths: M slf4j-api/src/main/java/org/slf4j/helpers/MessageFormatter.java M slf4j-jdk14/src/main/java/org/slf4j/impl/JDK14LoggerAdapter.java M slf4j-log4j12/src/main/java/org/slf4j/impl/Log4jLoggerAdapter.java Log Message: ----------- Merge pull request #15 from justdoo/master Fix for bug 264. Compare: https://github.com/qos-ch/slf4j/compare/c1dc48bdf8ef...0d3b1537b157

1 0

[Bug 266] New: Memory Leak: Clearing MDC context with Log4J
by bugzilla-daemon＠qos.ch 25 Sep '14

25 Sep '14

http://bugzilla.slf4j.org/show_bug.cgi?id=266 Summary: Memory Leak: Clearing MDC context with Log4J Product: SLF4J Version: 1.6.x Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 Component: Implementations AssignedTo: slf4j-dev(a)qos.ch ReportedBy: f.bantner(a)axon-e.de Recently after a long time log4j got it's problem with clearing the MDC context and the underlying ThreadLocal Hashmap fixed. S. https://issues.apache.org/bugzilla/show_bug.cgi?id=50486 This fixed a long running Problem with Tomcat freeing memory on reload. In order to do so, log4j's MDC got the clear method with 1.2.16 and with 1.2.17 fixed it so that it works. Log4j has an MDC adaptor for Log4J and it's own clear method. But instead of calling Log4J's clear it implements essentially (MDC.getContext()).clear() which only clears the HashMap but doesn't remove it from the ThreadLocal context resulting in a MemroryLeak. Short workaround: Instead of calling slf4j's MDC.clear() call log4j's MDC.clear() (but that is the exact opositit of what slf4j is made for) Simple Fix: change log4j's mdc adaptor to call MDC.clear() instead of MDC.getContext().clear(). More complex fix: If backward compatibility is an issue (like it was für log4j) than log4js solution can be applied here: Instead of calling MDC.clear() directly call it via reflexion if it exists and otherwise keep calling MDC.getContext().clear(). -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 3

[qos-ch/slf4j] bdbd1b: SimpleLogger: Fixed showDateTime default documenta...
by Matt Bishop 13 Sep '14

13 Sep '14

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: bdbd1b491ddf0447a57cd6e29e4c322e7b4cf9e5 https://github.com/qos-ch/slf4j/commit/bdbd1b491ddf0447a57cd6e29e4c322e7b4c… Author: Tobias Bieniek <Tobias.Bieniek(a)gmx.de> Date: 2014-08-21 (Thu, 21 Aug 2014) Changed paths: M slf4j-simple/src/main/java/org/slf4j/impl/SimpleLogger.java Log Message: ----------- SimpleLogger: Fixed showDateTime default documentation Commit: c1dc48bdf8efb3bbea247ea9b64e7549b051ae09 https://github.com/qos-ch/slf4j/commit/c1dc48bdf8efb3bbea247ea9b64e7549b051… Author: Matt Bishop <matt(a)thebishops.org> Date: 2014-09-13 (Sat, 13 Sep 2014) Changed paths: M slf4j-simple/src/main/java/org/slf4j/impl/SimpleLogger.java Log Message: ----------- Merge pull request #78 from Turbo87/patch-1 SimpleLogger: Fixed showDateTime default documentation Compare: https://github.com/qos-ch/slf4j/compare/fdafef025305...c1dc48bdf8ef

1 0

[Bug 320] New: More info at "Failed to load Class"
by bugzilla-daemon＠qos.ch 31 Jul '14

31 Jul '14

http://bugzilla.slf4j.org/show_bug.cgi?id=320 Priority: P5 Bug ID: 320 Assignee: slf4j-dev(a)qos.ch Summary: More info at "Failed to load Class" Severity: enhancement Classification: Unclassified OS: Linux Reporter: spam.trash(a)seznam.cz Hardware: PC Status: NEW Version: 1.7.x Component: Core API Product: SLF4J When SLF4J can't load some class, it just says SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details It would be very useful if it also printed out what classloader it used, and from which class it was initialized (taking this info from call stack). In modularized environments getting more used, this will become increasingly important. Thanks for considering. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 319] New: Missing version in pom files
by bugzilla-daemon＠qos.ch 07 Jul '14

07 Jul '14

http://bugzilla.slf4j.org/show_bug.cgi?id=319 Priority: P5 Bug ID: 319 Assignee: slf4j-dev(a)qos.ch Summary: Missing version in pom files Severity: blocker Classification: Unclassified OS: other Reporter: bdupraz.ext(a)deltadore.com Hardware: PC Status: NEW Version: 1.7.x Component: Implementations Product: SLF4J When using Ivy to resolve dependency in my project with this line: <dependency org="org.slf4j" name="slf4j-log4j12" rev="1.7.5" /> slf4j-api-1.7.5.jar and log4j-1.2.17.jar aren't resolve. I've open the ivy-1.7.5.xml file in Ivy cache, I've got this : <dependency org="org.slf4j" name="working@xxxxxxxx" rev="1.7.5" force="true" conf="compile->compile(*),master(*);runtime->runtime(*)"/> <dependency org="log4j" name="log4j" rev="working@xxxxxxxx" force="true" conf="compile->compile(*),master(*);runtime->runtime(*)"/> At working@xxxxxxxx, the xxxxxxxx are my machine host name. When I edit the file with dependency found on Maven central like this: <dependency org="org.slf4j" name="slf4j-api" rev="1.7.5" force="true" conf="compile->compile(*),master(*);runtime->runtime(*)"/> <dependency org="log4j" name="log4j" rev="1.2.17" force="true" conf="compile->compile(*),master(*);runtime->runtime(*)"/> It works as soon as I trigger a new resolve with Ivy. So I looked in the pom file on Maven Central and I found that the required version attribute in dependencies are missing. Here the extract of the pom file currently on Maven Central: <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> </dependency> </dependencies> and here is what it should be: <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.7.5</version> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.17</version> </dependency> </dependencies> This problem appears on every versions of slf4j-log4j12 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 318] New: Class org.apache.log4j.Category is missing method getAdditivity()
by bugzilla-daemon＠qos.ch 23 Jun '14

23 Jun '14

http://bugzilla.slf4j.org/show_bug.cgi?id=318 Priority: P5 Bug ID: 318 Assignee: slf4j-dev(a)qos.ch Summary: Class org.apache.log4j.Category is missing method getAdditivity() Severity: normal Classification: Unclassified OS: All Reporter: milo(a)milobjects.com Hardware: PC Status: NEW Version: unspecified Component: log4j-over-slf4j Product: SLF4J Log4J 1.2 has this method in its Category class. It's causing a method not found error when I use an existing code dependent on Log4J. -- You are receiving this mail because: You are the assignee for the bug.

1 0

Is Logging rate limit available in SLF4J?
by KRISHNA DURGAM 21 May '14

21 May '14

Thanks, Krishna Durgam

1 0

[Bug 317] New: erroneous migration turns returned Logger into LoggerFactory
by bugzilla-daemon＠qos.ch 04 May '14

04 May '14

http://bugzilla.slf4j.org/show_bug.cgi?id=317 Priority: P5 Bug ID: 317 Assignee: slf4j-dev(a)qos.ch Summary: erroneous migration turns returned Logger into LoggerFactory Severity: normal Classification: Unclassified OS: Windows 2000 Reporter: garret(a)globalmentor.com Hardware: PC Status: NEW Version: 1.7.x Component: slf4j-migrator Product: SLF4J The migrator turns this: public Logger getLogger() { return logger; } into this: public LoggerFactory.getLogger() { return logger; } I guess the migrator must be using some naive regex---but I would have thought it would have at least prevented whitespace in matching "Logger.getLogger(". -- You are receiving this mail because: You are the assignee for the bug.

1 1

[qos-ch/slf4j] fdafef: remove popup from download page
by Ceki Gulcu 04 Apr '14

04 Apr '14

Branch: refs/heads/master Home: https://github.com/qos-ch/slf4j Commit: fdafef0253050516f64a2af80f57840cbd785a38 https://github.com/qos-ch/slf4j/commit/fdafef0253050516f64a2af80f57840cbd78… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2014-04-04 (Fri, 04 Apr 2014) Changed paths: M slf4j-site/src/site/pages/download.html R slf4j-site/src/site/pages/js/jquery.cookies.2.2.0.js R slf4j-site/src/site/pages/js/popup.js Log Message: ----------- remove popup from download page

1 0

[qos-ch/slf4j]
by ceki 04 Apr '14

04 Apr '14

Branch: refs/tags/v1.7.7 Home: https://github.com/qos-ch/slf4j

1 0