commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16039] - Log4J shutdown not invoked?
Date Tue, 25 Mar 2003 17:43:48 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16039>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16039

Log4J shutdown not invoked?





------- Additional Comments From garyashley@3mv.biz  2003-03-25 17:43 -------
As a user of JBoss 3.0.6 w/ Tomcat 4.1.18, I wanted to make sure that any 
changes to Commons logging does not shutdown Log4J automatically.  I am not 
aware of any problems that I have, and it seems to function properly though I 
am in the early stages of testing this functionality.  

Struts makes a call to:
LogFactory.release(classLoader); 

which is where the comment that produced this bug report stems.  

I merely want to ensure caution is taken with the many interdependencies on the 
common's logging component.  Having one Struts application on the server 
shutting down logging for other applications, or for either Tomcat or JBoss 
would be very undesireable.

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


Mime
View raw message