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

Dominik Psenner closed LOG4NET-477.
-----------------------------------
    Resolution: Won't Fix

The method ActivateOptions configures the appender based on the configuration 
options set. This method should be called only once when the appender is 
initialized. This method then does several heavy lifting operations that take 
long enough so that they should not be done on every log event.

This test case calls the method way more often than what it should be and this 
even fro multiple threads which again should not happen. If people use the 
appender like this the way how they use it must be adjusted to interact better 
with how log4net works.

For this reason I'm closing this issue as won't fix. If you feel that this 
decision is wrong, feel free to reopen the issue but please provide a real 
world example or usecase where the ActivateOptions method must be effectively 
called so many times.

> AdoNetAppender.ActivateOptions hangs when called from multiple threads
> ----------------------------------------------------------------------
>
>                 Key: LOG4NET-477
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-477
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.13
>         Environment: Windows 7, Windows 10
>            Reporter: Marcin Sitko
>              Labels: performance
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> When AdoNetAppender.ActivateOptions is called from multiple threads (amount 
> of threads depends on machine) it could take 15, 30 and more seconds to 
> complete. Normally it takes less than 100 milliseconds. I prepared sample 
> project which demonstrates this issue (you may need to increase amount of 
> threads, it vary on machine on which test is ran ) 
> https://github.com/marcin-sitko/Log4NetBug . From process dumps it seems that 
> it hangs on waiting for connection or on disposing a connection. Please take 
> a look at this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to