tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33932] - Problem with common logging - uses wrong logger
Date Tue, 15 Mar 2005 13:44:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33932>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33932


c.grigoroscuta@moodmedia.ro changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From c.grigoroscuta@moodmedia.ro  2005-03-15 14:44 -------
I think I did not make myself very clear. I saw several classes from server/libs
(BeanUtilsBean was one of them) that maintained references to Logger instances
loaded by web app class loader, through the "log" static field.

>From my point of view, as long as common-beanutils and common-logging exist in
server/lib, they are part of Tomcat web server. For the Tomcat user's point of
view, bugs in the versions of these libs delivered with Tomcat are also bugs of
Tomcat. I understand the tomcat developer's point of view, but you must also
understand the user's point of view. 

Looking closer, I think the problem might be in common-logging, in
LogFactoryImpl, that user the context class loader to load the logger instance.
If a class from server/lib, loaded by Tomcat's class loader is first accessed
from a web application, its logger will be loaded by the web application's class
loader, and this class will always maintain this strong reference to the logger,
no matter what cleanup you do in commons-logging when I stop the application.

If this is the case, it is indeed a bug in commons-logging, but as far as I am
concerned, it's also a bug is tomcat, as it is delivered with commons-logging as
a part of it.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message