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=36342>. 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=36342 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO ------- Additional Comments From [EMAIL PROTECTED] 2006-08-01 18:46 ------- Marking as need info for now, but will eventually likely close as invalid. Your report doesn't go into enough detail to reproduce the problem or offers any suggested remedy. At this late in the lifetime of log4j any significant change in behavior is unlikely, so any suggested modification would have to be very conservative so that it would address your issue without break apps that depend on the current behavior. You do not mention how you are configuring log4j. Default configuration using log4j.properties or log4j.xml should only be called once per log4j instance. Your report suggests that you may be explicitly calling a configurator multiple times. If so, there is not much opportunity to change the behavior since it would also affect a console app for example that makes multiple calls to a configurator. There is a provision (in log4j 1.3, I believe) to support multiple logging domains for just such as scenario as you describe, but I'm not all that familiar with it. Ask on log4j-user if you are interested. -- 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]
