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

[ https://issues.apache.org/jira/browse/LOG4NET-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609569#comment-15609569 ] Dominik Psenner commented on LOG4NET-528: - There is not enough information in this issue to allow

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

VENKATA NAGA RADHAKRISHNA SEGU created LOG4NET-528: -- Summary: AdoNetAppender giving .net lock Key: LOG4NET-528 URL: https://issues.apache.org/jira/browse/LOG4NET-528 Project: Log4net

RE: Better support for logging from an Appender

Appenders that log is immensely hard to implement if not separated entirely from the normal logging. Therefore there is the loglog class. It could be a feature to allow the configuration of loglog appenders under the precondition that those appenders do not append events back into the logging

[GitHub] log4net issue #35: Wip/app settings

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/35 I've just realized there is no documentation outside of the API docs for the other `PatternStringConverter`s either, so yes, XML comments should be sufficient - and you've already provided that. I

[jira] [Commented] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[ https://issues.apache.org/jira/browse/LOG4NET-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609324#comment-15609324 ] ASF GitHub Bot commented on LOG4NET-526: Github user JJoe2 commented on the issue:

[GitHub] log4net issue #35: Wip/app settings

Github user JJoe2 commented on the issue: https://github.com/apache/log4net/pull/35 I’ll be happy to do the unit tests and possibly the doc. Are suitable XML comments enough? Now this is added, I’ll also be thinking about the next step, which is to allow the

[jira] [Commented] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[ https://issues.apache.org/jira/browse/LOG4NET-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609311#comment-15609311 ] ASF GitHub Bot commented on LOG4NET-526: Github user asfgit closed the pull request at:

[GitHub] log4net pull request #35: Wip/app settings

Github user asfgit closed the pull request at: https://github.com/apache/log4net/pull/35 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (LOG4NET-526) Add appSetting conversion pattern to PatternString

[ https://issues.apache.org/jira/browse/LOG4NET-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609299#comment-15609299 ] ASF GitHub Bot commented on LOG4NET-526: Github user bodewig commented on the issue:

[GitHub] log4net issue #35: Wip/app settings

Github user bodewig commented on the issue: https://github.com/apache/log4net/pull/35 I've added your converter, many thanks. Tests would be good and we need documentation before we can close LOG4NET-526. --- If your project is set up for it, you can reply to this email and

RE: Better support for logging from an Appender

Thanks for the response. After more thought and some tests, this idea is a non-starter. 1. Hierarchy.Logger.CallAppenders acquires a ReaderWriterLockSlim instance that doesn't allow recursion (the default LockRecursionPolicy.NoRecursion). Thus if a synchronous appender attempts to log, it