[
https://issues.apache.org/jira/browse/LOG4NET-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907982#comment-14907982
]
Marcin Sitko commented on LOG4NET-477:
--------------------------------------
Thank you for replying. We encountered this issue in our REST API application,
there were different connection strings in our application and we refreshed
configuration in each request. You probably could imagine that we started
observing very high deviation in our performance tests because most of the
request were handled quite fast but some of them were stuck (they were waiting
on ActivateOptions completion). I totally agree with you that it is our design
flaw that we need to refresh configuration so often. However at least it may be
worth to mention this in doc that this method could cause such issue.
Especially that it executes quite fast (around 100 ms ) even when it is called
from multiple threads and then after reaching some "critical" amount of threads
execution time of some of the calls is increased dramatically (to 15 seconds ,
30 seconds etc.)
> 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)
