February 2015 - slf4j-dev - mailman3.qos.ch

[Bug 201] New: Need ability to shutdown loggers and flush appenders
by bugzilla-daemon＠pixie.qos.ch 03 Mar '15

03 Mar '15

http://bugzilla.slf4j.org/show_bug.cgi?id=201 Summary: Need ability to shutdown loggers and flush appenders Product: SLF4J Version: 1.6.x Platform: PC OS/Version: Windows NT Status: NEW Severity: enhancement Priority: P1 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: mike.schall(a)gmail.com There needs to be a way to shutdown logging and flush async appenders so when a process is closing, all log events are written before the process is closed. Should ILoggerFactory have a shutdown or stop method? It could shutdown whatever logging back end I'm using? For log4j it would call - org.apache.log4j.LogManager.getLoggerRepository().shutdown(); For logback it would call - loggerContext.stop() Other back ends - ??? This is required to allow me to not reference logging back ends explicitly in my code to shutdown successfully without losing events. Discussion about this is happening on the user list at - http://www.qos.ch/pipermail/logback-user/2010-September/001816.html -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 18

[Bug 327] New: Not able to resolve method org.apache.log4jCategory.getParent
by bugzilla-daemon＠qos.ch 24 Feb '15

24 Feb '15

http://bugzilla.slf4j.org/show_bug.cgi?id=327 Priority: P5 Bug ID: 327 Assignee: slf4j-dev(a)qos.ch Summary: Not able to resolve method org.apache.log4jCategory.getParent Severity: enhancement Classification: Unclassified OS: Windows NT Reporter: him_bhar(a)hotmail.com Hardware: PC Status: NEW Version: 1.7.x Component: log4j-over-slf4j Product: SLF4J I am using a third-party API which internally uses a custom logger based on log4j. Replacing the log4j with log4j-over-slf4j doesn't help as one of the method is not present in the log4j-over-slf4j. Can't share much of the trace as data sharing policy: Caused by: java.lang.NoSuchMethodError: org.apache.log4j.Logger.getParent()Lorg/apache/log4j/Category; Verified the same in codebase of log4j-over-slf4j and this method getParent() is not present in the jar. Whereas for log4j v 1.2.17, this is present. public final Category getParent() { return this.parent; } -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 326] New: Get wrong %class content in wrapper class
by bugzilla-daemon＠qos.ch 04 Feb '15

04 Feb '15

http://bugzilla.slf4j.org/show_bug.cgi?id=326 Priority: P5 Bug ID: 326 Assignee: slf4j-dev(a)qos.ch Summary: Get wrong %class content in wrapper class Severity: enhancement Classification: Unclassified OS: Windows NT Reporter: monkeyk1987(a)gmail.com Hardware: PC Status: NEW Version: 1.7.x Component: jul-to-slf4j Product: SLF4J I define a Java Object: LogHelper, use it wrapper the logger operations, the main codes as follow: private final Logger logger; protected LogHelper(Class clazz) { this.logger = LoggerFactory.getLogger(clazz); } public void info(String msg) { if (logger.isInfoEnabled()) { logger.info(currentUser() + LOG_DELIMITER + msg); } } ... Then when i want to record log use LogHelper replace Logger, code as follow: private static final LogHelper LOG = LogHelper.create(Activity.class); In the log file can not get the current Class name(Activity class), always get LogHelper class name, the log content look like: 2014-11-28 14:39:15 xxx.infrastructure.log.LogHelper:89 - lisz|Start to generate [2014-10] Attendance-Report... the log appender configuration is: <appender name="SchedulerAppender" class="ch.qos.logback.core.FileAppender"> <file>../logs/xxx_scheduler.log</file> <append>true</append> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss} %class:%line - %msg%n</pattern> </encoder> </appender> We expect the %class is Activity class, not LogHelper class, but it is failed. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 133] Add ability to log at a dynamic level
by bugzilla-daemon＠qos.ch 02 Feb '15

02 Feb '15

http://bugzilla.slf4j.org/show_bug.cgi?id=133 Marco <zakmck73(a)yahoo.it> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zakmck73(a)yahoo.it --- Comment #16 from Marco <zakmck73(a)yahoo.it> --- Just stumbled upon this problem and agree with embedding the Lidalia extension into SLF4J. It misses something like getCurrentLogLevel() though, which would be useful as well. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 323] New: slf4j not logging VERBOSE and DEBUG messages, no matter what is Logcat's loglevel
by bugzilla-daemon＠qos.ch 02 Feb '15

02 Feb '15

http://bugzilla.slf4j.org/show_bug.cgi?id=323 Priority: P5 Bug ID: 323 Assignee: slf4j-dev(a)qos.ch Summary: slf4j not logging VERBOSE and DEBUG messages, no matter what is Logcat's loglevel Severity: normal Classification: Unclassified OS: All Reporter: zalavaari(a)gmail.com Hardware: Other Status: NEW Version: 1.7.x Component: slf4j-android Product: SLF4J It seems on android platform the isLoggable() method is always returns false for VERBOSE and DEBUG (no matter what is the actal loglevel is), so it should not be called before calling Log.d and Log.v The only slf4j version I know of where the DEBUG & VERBOSE logs are working is 1.6.1-RC1 -- You are receiving this mail because: You are the assignee for the bug.

1 1