[slf4j-dev] [Bug 72] New: Performance and the JDK1.4 logger
bugzilla-daemon at pixie.qos.ch
bugzilla-daemon at pixie.qos.ch
Thu Feb 14 19:47:00 CET 2008
http://bugzilla.slf4j.org/show_bug.cgi?id=72
Summary: Performance and the JDK1.4 logger
Product: SLF4J
Version: unspecified
Platform: All
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P1
Component: Implementations
AssignedTo: dev at slf4j.org
ReportedBy: listid at qos.ch
Accoding to Ian Carr, the fillCallerData method is called even for disabled log
statements.
private void log(String callerFQCN, Level level, String msg, Throwable t) {
// millis and thread are filled by the constructor
LogRecord record = new LogRecord(level, msg);
record.setLoggerName(getName());
record.setThrown(t);
fillCallerData(callerFQCN, record); <-- bad
logger.log(record);
}
For more information see
http://www.slf4j.org/pipermail/user/2008-February/000486.html
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the slf4j-dev
mailing list