You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Dominik Psenner (JIRA)" <ji...@apache.org> on 2012/05/23 08:19:41 UTC

[jira] [Comment Edited] (LOG4NET-342) Add a way to prevent silent failure

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

Dominik Psenner edited comment on LOG4NET-342 at 5/23/12 6:17 AM:
------------------------------------------------------------------

One could add a global boolean configuration named like "EnableExceptionThrowing" that is "False" by default. In case one wants to test something he would then be able to change that flag in the app.config. Once set to "True" all exceptions thrown would no longer be ignored silently, but thrown up to the calling application so that the exception can be debugged/handled in some other way.

I just targeted it for 1.2.12 since it should be doable.
                
      was (Author: nachbarslumpi):
    One could add a global boolean configuration named like "EnableExceptionThrowing" that is "False" by default. In case one wants to test something he would then be able to change that flag in the app.config. Once set to "True" all exceptions thrown would no longer be ignored silently, but thrown up to the calling application so that the exception can be debugged/handled in some other way.
                  
> Add a way to prevent silent failure
> -----------------------------------
>
>                 Key: LOG4NET-342
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-342
>             Project: Log4net
>          Issue Type: New Feature
>            Reporter: Joachim Zobel
>            Priority: Minor
>             Fix For: 1.2.12
>
>
> I spent most of the day trying to find out why logging is not working on my dev system but not on test. There should be a way to force error reporting by throwing (possibly unhandled) exceptions. This could be done by adding a required flag to the appenders and another flag that requires a least one working appender.
> I am not sure about a good way to implement this, I would just love it if my favourite tool to end silent failure could stop failing silently. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira