You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Davyd McColl (Jira)" <ji...@apache.org> on 2020/09/14 06:30:00 UTC

[jira] [Resolved] (LOG4NET-528) AdoNetAppender giving .net lock

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

Davyd McColl resolved LOG4NET-528.
----------------------------------
    Resolution: Fixed

Hi

In a bid to get the machinery all going again, I'm closing out old issues, especially when:
- they are against older versions of log4net ( < 2)
- they have no associated pull request
- they are unlikely to receive attention because they're wishlist material

I'm doing this to try to increase the signal-to-noise ratio so that it's more likely
that issues which can be attended to get the attention they deserve.

I'm not doing this because your contribution isn't important. On the contrary, if
the problem still persists, please raise a new issue -- I'd like to know about it.


> AdoNetAppender giving .net lock
> -------------------------------
>
>                 Key: LOG4NET-528
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-528
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.15
>         Environment: Windows Server 2008 R2, WCF Web Http Service, Dot Net 4.0
>            Reporter: VENKATA NAGA RADHAKRISHNA SEGU
>            Priority: Critical
>
> Dear Sir, 
> I am using log4net adonetappender and logging web service info and error messages. I am getting Dot Net Lock issue when there are more concurrent users (approx 300). Please advice me what to do in this case. 
> Regards,
> Venkata



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