March 2010 - slf4j-dev - mailman3.qos.ch

[Bug 173] New: slf4j android: Android throws an IllegalArgumentException when Log Tag length exceeds 23 characters
by bugzilla-daemon＠pixie.qos.ch 11 Sep '13

11 Sep '13

http://bugzilla.slf4j.org/show_bug.cgi?id=173 Summary: slf4j android: Android throws an IllegalArgumentException when Log Tag length exceeds 23 characters Product: SLF4J Version: 1.5.x Platform: Other OS/Version: other Status: NEW Severity: blocker Priority: P1 Component: Implementations AssignedTo: slf4j-dev(a)qos.ch ReportedBy: lorecarra(a)gmail.com I don't know if the 23-characters long tag limitation has been removed in later releases, but, unfortunately, Android 1.1 has it. I think the tag length should be checked and the tag eventually trimmed in order to avoid incurring in this exception without having to change the application logging code. The check is performed into the native method android.util.Log.isLoggable() To reproduce the problem in Android 1.1: String ALLOWED_TAG = "abcdefghijklmnopqrstuvw"; String TOO_LONG_TAG = "abcdefghijklmnopqrstuvwxyz"; Log.i(ALLOWED_TAG, "blabla"); Log.i(TOO_LONG_TAG, "blabla"); -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 19

[Bug 166] New: please add OSGI informations to jul-to-slf4j-1.5.10.jar
by bugzilla-daemon＠pixie.qos.ch 02 Sep '11

02 Sep '11

http://bugzilla.slf4j.org/show_bug.cgi?id=166 Summary: please add OSGI informations to jul-to-slf4j-1.5.10.jar Product: SLF4J Version: 1.5.x Platform: All OS/Version: Mac OS X 10.3 Status: NEW Severity: normal Priority: P3 Component: Unspecified AssignedTo: slf4j-dev(a)qos.ch ReportedBy: ekke(a)ekkes-corner.org jul-to-slf4j-1.5.10.jar MANIFEST.MF is missing OSGI Informations ... Import-Package: org.slf4j;version="1.5.10", org.slf4j.spi;version="1.5.10" Export-Package: org.slf4j.bridge;version="1.5.10" ... so you have to wrap it by yourself or as workaround use the Bundle provided by SpringSource: http://www.springsource.com/repository/app/bundle/version/detail?name=com.s… ----- thx ekke -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

[Bug 163] New: Copy & paste of LoggerFactory.getLogger
by bugzilla-daemon＠pixie.qos.ch 19 Jul '11

19 Jul '11

http://bugzilla.slf4j.org/show_bug.cgi?id=163 Summary: Copy & paste of LoggerFactory.getLogger Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: thomas.tom.mueller(a)gmail.com This is a feature request. Currently, when I create a new logger in a class, I copy & paste the following line from another class: private static Logger log = LoggerFactory.getLogger(AcmeImpl.class); Sometimes I forget to change the class name. SLF4J could help me here. I suggest to add a new method, so the class name is not required, so that I can copy & paste the line without having to remember that I have to change the class name. Also, it's a bit shorter: private static Logger log = LoggerFactory.getCallerClassLogger(); This is copy & paste friendly. The implementation is tricky, but trivial once you understand it: getCallerClassLogger() { return getLogger(new Error().getStackTrace()[1].getClassName()); } There is a project that tries to solve the copy & paste problem: http://code.google.com/p/morbok/ -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 40

[Bug 174] New: Handling of unknown priorities is different ( throwing an IllegalStateException ) than in log4j (defaulting to Priority. DEBUG)
by bugzilla-daemon＠pixie.qos.ch 10 Nov '10

10 Nov '10

http://bugzilla.slf4j.org/show_bug.cgi?id=174 Summary: Handling of unknown priorities is different (throwing an IllegalStateException ) than in log4j (defaulting to Priority.DEBUG) Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: torsten(a)springide.org Log4j silently converts an unknown Priority (given as int value or string) to the default of Priority.DEBUG (see default of switch-case in "Level.toLevel()"). If log4j-over-slf4j gets an unknown instance of Priority for it various "log()" methods then it throws an IllegalStateException (see default of switch-case in "Category.priorityToLevelInt()"): Caused by: java.lang.IllegalStateException: Unknown Priority TRACE at org.apache.log4j.Category.priorityToLevelInt(Category.java:316) at org.apache.log4j.Category.log(Category.java:287) Ok, now you're asking for the actual usecase for someone calling "Category.log()" with an invalid instance of Priority: We have a legacy application which has it's own logging abstraction extending (a very old version of) log4j with it's own log levels. Unluckily, here someone defined a TRACE level with a different value for "Priority.TRACE_INT" than Log4js "Level.TRACE_INT". -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 171] New: OSGi: Add an Import-Package to log4j-overslf4j's MANIFEST.MF
by bugzilla-daemon＠pixie.qos.ch 05 Apr '10

05 Apr '10

http://bugzilla.slf4j.org/show_bug.cgi?id=171 Summary: OSGi: Add an Import-Package to log4j-overslf4j's MANIFEST.MF Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Linux Status: NEW Severity: blocker Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: hmalphettes(a)intalio.com Hi, while working on http://bugzilla.slf4j.org/show_bug.cgi?id=170 I noticed that org.apache.log4j.Log4jLoggerFactory requires org.slf4j.helpers.Util It should be added to log4j-over-slf4j's MANIFEST as an Import-Package: The difference is at the very end of: http://github.com/hmalphettes/slf4j/commit/2d30df3bd74e920d505308b322579d6f… log4j-over-slf4j/src/main/resources/META-INF/MANIFEST.MF @@ -3,4 +3,4 @@ Bundle-SymbolicName: log4j.over.slf4j Bundle-Name: log4j-over-slf4j Export-Package: org.apache.log4j -Import-Package: org.slf4j, org.slf4j.spi +Import-Package: org.slf4j, org.slf4j.helpers, org.slf4j.sp Thanks! Hugues -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 164] New: NPE on LoggerFactory.singleImplementationSanityCheck
by bugzilla-daemon＠pixie.qos.ch 04 Apr '10

04 Apr '10

http://bugzilla.slf4j.org/show_bug.cgi?id=164 Summary: NPE on LoggerFactory.singleImplementationSanityCheck Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: joakim.erdfelt(a)gmail.com This occurs on slf4j-api 1.5.7 and 1.5.8 when using logback 0.9.18 It does not occur on slf4j-api 1.5.6 Note: the environment being used has various java.endorsed.dirs setup where the logging is initialized. This being not very normal, it could be the reason for this NPE, as I believe LoggerFactory.class.getClassLoader() will return null in this scenario. java.lang.NullPointerException at org.slf4j.LoggerFactory.singleImplementationSanityCheck(LoggerFactory.java:192) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:113) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:269) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:242) at org.eclipse.jetty.util.log.Slf4jLog.<init>(Slf4jLog.java:33) at org.eclipse.jetty.util.log.Slf4jLog.<init>(Slf4jLog.java:28) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 175] New: Race Condition in SubstituteLoggerFactory
by bugzilla-daemon＠pixie.qos.ch 04 Apr '10

04 Apr '10

http://bugzilla.slf4j.org/show_bug.cgi?id=175 Summary: Race Condition in SubstituteLoggerFactory Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: rimovm(a)centercomp.com Here's the relevant snippet from a test case: java.lang.ArrayIndexOutOfBoundsException: 10 at java.util.ArrayList.add(ArrayList.java:352) at org.slf4j.helpers.SubstituteLoggerFactory.getLogger(SubstituteLoggerFactory.java:59) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:249) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:261) at org.picocontainer.gems.monitors.Slf4jComponentMonitor.getLogger(Slf4jComponentMonitor.java:285) at org.picocontainer.gems.monitors.Slf4jComponentMonitor.instantiating(Slf4jComponentMonitor.java:161) SubstituteLoggerFactory doesn't lock provide synchronization sharing the loggerNameList. Thanks, -Mike (R) -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 170] New: Add log4j's NDC support in log4j-over-slf4j
by bugzilla-daemon＠pixie.qos.ch 04 Apr '10

04 Apr '10

http://bugzilla.slf4j.org/show_bug.cgi?id=170 Summary: Add log4j's NDC support in log4j-over-slf4j Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Linux Status: NEW Severity: blocker Priority: P1 Component: log4j-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: hmalphettes(a)intalio.com It would be nice to support log4j's NDC class. For example http://opensaml.org depends on that. It is a straight forward port that simply delegate all log4j's NDC calls to slf4j's NDC static methods. This commit http://github.com/hmalphettes/slf4j/commit/2d30df3bd74e920d505308b322579d6f… Does add such support and behaves well with opensaml. I also found a missing Import-Package in log4j-over-slf4j's MANIFEST for OSGi. org.apache.log4j.Log4jLoggerFactory requires org.slf4j.helpers.Util Cheers, Hugues. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 4

[Bug 161] New: log4j-over-slf4j doesn't implement org.apache.log4j.spi. RootCategory
by bugzilla-daemon＠pixie.qos.ch 04 Apr '10

04 Apr '10

http://bugzilla.slf4j.org/show_bug.cgi?id=161 Summary: log4j-over-slf4j doesn't implement org.apache.log4j.spi.RootCategory Product: SLF4J Version: 1.5.x Platform: PC OS/Version: Windows XP Status: NEW Severity: major Priority: P1 Component: log4j-over-slf4j AssignedTo: dev(a)slf4j.org ReportedBy: boris(a)granveaud.com Some libraries (for example SmartGWT EE) use the classes located in package org.apache.log4j.spi. These classes should be emulated in log4j-over-slf4j. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 4

[Bug 31] Varargs for Logger methods
by bugzilla-daemon＠pixie.qos.ch 31 Mar '10

31 Mar '10

http://bugzilla.slf4j.org/show_bug.cgi?id=31 --- Comment #81 from Thorbjørn Ravn Andersen <thorbjoern(a)gmail.com> 2010-03-31 19:02:20 --- (In reply to comment #80) > An added bit of information. As part of my work on Log4j 2.0 I discovered that > there is significant overhead in using varargs. The technique used by SLF4J of > providing 1, 2, 3 parameters and then 3 + varargs reduces the overhead > considerably. This was true even when there were no parameters being passed. Could you elaborate on the overhead? I thought a "new Object[] {...}" was being produced by the compiler and that was that? -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0