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=32662>. 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=32662 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-09 00:24 ------- It would seem to me that Vedran is right that a webapp that uses commons-logging should not need to make direct calls to log4j on shutdown (this is what you were suggesting, Robert?) However as Robert states, the solution needs care; if two webapps are using log4j and one of them is reloaded it would be very unpleasant if the other webapp suddenly had its logging implementation shut down. So before adding a call to LogManager.shutdown in log4j, it would be wise to determine whether this would happen or not. I would initially assume that log4j.jar would be deployed in the webapp-specific libraries. As such, a separate copy should exist within each webapp (different classloaders used) and therefore calling shutdown on one would *not* affect the other. However I'm no expert on containers; I know that in some cases containers want to provide the underlying logging implementation so that logging is centralised for all webapps. If the container chooses log4j as its centralised logging implementation, then what? -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
