You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2020/04/04 22:30:05 UTC

[jira] [Updated] (LOG4NET-569) If I change the name of 'section' name present under configsections other than "log4net", logging is not happening

     [ https://issues.apache.org/jira/browse/LOG4NET-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralph Goers updated LOG4NET-569:
--------------------------------

LOG4NET is now dormant.  

> If I change the name of 'section' name present under configsections other than "log4net", logging is not happening
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-569
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-569
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 1.2.10
>            Reporter: Ezhumalai
>            Priority: Major
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> I have an parent application and under that many child applications are running. To log the errors separately for each application, i decided to add log4net section in all the web.config of all applications. It seems like the configuration values are getting inherited from the parent to child applications giving the error "There is an entry already present for the name log4net". I am looking whether we can rename the 'section'  name from 'log4net' to 'log4netNew'  to avoid the conflicts with the child applications configuration values. Please let me know.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)