logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-504) Exception mode during configuration
Date Wed, 03 Feb 2016 09:34:39 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130107#comment-15130107

Dominik Psenner commented on LOG4NET-504:

You can enable log4net's internal logging (see faq). Doesn't that help you figure out why
things do not work as expected? Further I've reduced the priority of this issue.

> Exception mode during configuration
> -----------------------------------
>                 Key: LOG4NET-504
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-504
>             Project: Log4net
>          Issue Type: Wish
>          Components: Other
>            Reporter: Gregory Zak
>            Priority: Minor
> When getting started with log4net configuration for the first time, it would be extremely
helpful to have a mode where a call to one of the various {{.Configure()}} methods would throw
exceptions as they were encountered, rather than silently sailing past them / aborting.
> I'm currently absolutely stuck with [this issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file]
on stackoverflow, and I've already tried all the expected suggestions (enable trace debugging,
check for config errors explicitly, etc etc), but I'm still staring at a silent failure (the
most frustrating kind of failure) unable to make any progress.
> Don't make me switch to NLog guys!

This message was sent by Atlassian JIRA

View raw message