bernard mcgourty created LOG4NET-335:
----------------------------------------
Summary: Lost the ability to monitor changes to logger config
files when you call ConfigureAndWatch multiple times with different Config File
Names - worked fine on 1.2.10.0
Key: LOG4NET-335
URL: https://issues.apache.org/jira/browse/LOG4NET-335
Project: Log4net
Issue Type: Bug
Components: Other
Affects Versions: 1.2.11
Environment: Windows Server 2008 R2
Reporter: bernard mcgourty
Priority: Blocker
We had a class that wraps log4net that is in a shared assembly, multiple
components in our application create instances to the Log 4 Net Wrapper, each
component has its own log config file.
When the Log4Net wrapper class is constructed it uses log4net.Logmanager to
ConfigureAndWatch the log config file passed in to it by the calling component.
We recently upgraded from log4net 1.2.10.0 to 1.2.11.0 and log4net no longer
detects when the log configuration file is modified. I looked at the source
code fro 1.2.11.0 and it appears that it only allows one
ConfigureAndWatchHandler object and if you attempt to ConfigureAndWatch more
than one logger config file, the previous one is Disposed, thereby removing the
ability to detect config file changes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
