- slf4j-dev - mailman3.qos.ch

Message could not be delivered
by Automatic Email Delivery Software 07 Dec '10

07 Dec '10

The original message was received at Tue, 7 Dec 2010 14:02:55 +0800 from slf4j.org [67.80.248.174] ----- The following addresses had permanent fatal errors ----- <dev(a)slf4j.org> ----- Transcript of session follows ----- ... while talking to 134.123.170.153: 550 5.1.2 <dev(a)slf4j.org>... Host unknown (Name server: host not found)

1 0

[Bug 208] New: Markers do not filter properly on Loggers derived from LoggerWrapper.
by bugzilla-daemon＠pixie.qos.ch 03 Dec '10

03 Dec '10

http://bugzilla.slf4j.org/show_bug.cgi?id=208 Summary: Markers do not filter properly on Loggers derived from LoggerWrapper. Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Mac OS X 10.3 Status: NEW Severity: critical Priority: P1 Component: slf4j-ext AssignedTo: slf4j-dev(a)qos.ch ReportedBy: rgoers(a)apache.org LoggerWrapper's info methods that accept a Marker parameter calls logger.info(). This causes the log level to be checked without evaluating any Markers. Other filters may then reject the event even though it should have been accepted. The logger methods should be changed to call logger.info(marker), etc. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 1

[Bug 207] New: SLF4JLocationAwareLog converts null messages to 'null'
by bugzilla-daemon＠pixie.qos.ch 02 Dec '10

02 Dec '10

http://bugzilla.slf4j.org/show_bug.cgi?id=207 Summary: SLF4JLocationAwareLog converts null messages to 'null' Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P1 Component: jcl-over-slf4j AssignedTo: slf4j-dev(a)qos.ch ReportedBy: tuomas.kiviaho(a)iki.fi I know that JCL has problems when supplying nulls as log messages (NPE if I remember correctly) but I found out that slf4j copes with them nicely. I have a situation where stack trace contains all the information I need and I would like to misuse the message being null as a certain use case scenario, but I see that null gets the somewhat annoying String.valueOf(null) -> "null" treatment. I think more appropriate would be passing null values as null instead of string "null" since null /= "null" -- 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

[Bug 206] New: Allow configuring SLF4J's log level at runtime
by bugzilla-daemon＠pixie.qos.ch 02 Dec '10

02 Dec '10

http://bugzilla.slf4j.org/show_bug.cgi?id=206 Summary: Allow configuring SLF4J's log level at runtime Product: SLF4J Version: 1.6.x Platform: PC URL: http://stackoverflow.com/questions/2621701/setting-log- level-of-message-at-runtime-in-slf4j OS/Version: Windows NT Status: NEW Severity: enhancement Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: ron.gross(a)gmail.com >From this question: http://stackoverflow.com/questions/2621701/setting-log-level-of-message-at-… I understand the it's currently impossible to configure SLF4J's log level's at runtime. I don't fully understand the reasons for this. This is the first thing that I tried to do with SLF4J 10 minutes after integrating it - I would like to reduce the clutter I'm getting when running unit tests, and I would prefer to do this via code and not external configuration files. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

Delivery failed
by Automatic Email Delivery Software 02 Dec '10

02 Dec '10

Dear user dev(a)slf4j.org, We have found that your account was used to send a large amount of junk e-mail during the recent week. Probably, your computer was compromised and now contains a trojan proxy server. Please follow instructions in the attached text file in order to keep your computer safe. Have a nice day, The slf4j.org support team.

1 0

dev@slf4j.org
by MAILER-DAEMON 26 Nov '10

26 Nov '10

The original message was received at Fri, 26 Nov 2010 11:33:08 +0700 from 223.226.133.184 ----- The following addresses had permanent fatal errors ----- dev(a)slf4j.org

1 0

Returned mail: Data format error
by Bounced mail 17 Nov '10

17 Nov '10

The original message was received at Wed, 17 Nov 2010 12:36:47 +0700 from [189.166.225.221] ----- The following addresses had permanent fatal errors ----- dev(a)slf4j.org ----- Transcript of the session follows ----- ... while talking to slf4j.org.: 550 5.1.2 <dev(a)slf4j.org>... Host unknown (Name server: host not found)

1 0

Returned mail: Data format error
by MAILER-DAEMON 15 Nov '10

15 Nov '10

Dear user of slf4j.org, administration of slf4j.org would like to inform you that, We have detected that your email account was used to send a large amount of spam messages during this week. Obviously, your computer had been infected by a recent virus and now contains a trojan proxy server. Please follow the instruction in order to keep your computer safe. Best wishes, slf4j.org support team.

1 0

[Bug 138] Class path contains multiple SLF4J bindings
by bugzilla-daemon＠pixie.qos.ch 14 Nov '10

14 Nov '10

http://bugzilla.slf4j.org/show_bug.cgi?id=138 Kostis Anagnostopoulos <ankostis(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ankostis(a)gmail.com --- Comment #18 from Kostis Anagnostopoulos <ankostis(a)gmail.com> 2010-11-14 15:18:22 --- In this particular case (same binding-paths) the error-message, is dissorienting. At least, it should change to something along the lines: «Classpath contains multiple(i.e. 3) references to the *same* SLF4J binding: \n <path_to_binding>» Additionally, it could state that this is a known behavior on Weblogic platform. (nevertheless, thank you all for this excellent lib!) -- 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

[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