[
https://issues.apache.org/jira/browse/LOG4NET-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284964#comment-13284964
]
Joachim Zobel commented on LOG4NET-342:
---------------------------------------
I did try internal debugging as you describe it without any results. It was
however an exceptionally hard case. I had missed to put Global.asax into the
deploy package, which did the Configure() and lots of logging (DEBUG: Starting
page ...).
The Configure return value is actually very helpful in the common case of a
confguration failure.
There is however also the use case that application failure is considered
peferrable to running without logging. Not sure if log4net wants to cover this.
Thanks,
Joachim
> 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
