[slf4j-dev] [Bug 15] SLF4JLog 'logger' field nulled by Tomcat 5.5.15

[bugzilla-daemon at gil.qos.ch]

http://bugzilla.slf4j.org/show_bug.cgi?id=15





------- Additional Comments From matt.invoices at llmj.com  2006-02-08 21:41 -------

I have reported the bug on Tomcat Bugzilla.  We'll see what they have to say
about it.

I did think of another possible "fix" on SLF4J's end, but I'm not sure how
acceptable it would be.  It's very simple: push loggerMap's cache down one level
and cache the Log4J Logger instances instead of the SLF4JLog instances that
reference them.  Then simply return a new SLF4JLog instance every time
SLF4JLogFactory.getLog() is called.  Since these are loggers, any performance
hit from this would probably be most noticeable during application startup.  It
would only be a real issue if applications are commonly using instance loggers
on classes of which many instances are created at runtime.

Of course, I know basically nothing about the typical usage patterns of a
logging framework.  For all I know, all of these (admittedly unnecessary)
SLF4JLog instantiations could be expensive in some scenarios.  Just wanted to
throw it out there..


-- 
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.