[
https://issues.apache.org/jira/browse/LOG4NET-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Smith updated LOG4NET-331:
-------------------------------
Description: When using AdoNetAppender, with a conversion pattern of
'%aspnet-request{REMOTE_ADDR}', and I attempt to write a log entry during the
Application_Start event, it throws an error (internally) and stops working. The
error refers to "...Request is not available in this context.." which makes
sense because its only in the Application_Start event. However the appender
should accommodate this situation and log null, not throw an error. The
RollingFileAppender, for instance, handles this gracefully. (was: When using
AdoNetAppender, with a conversion pattern of '%aspnet-request{REMOTE_ADDR}',
and I attempt to write a log entry during the Application_Start event, it
throws an error (internally) and stops working. The error refers to "...Request
is not available in this context.." which makes sense because its only in the
Application_Start event. However the appender should accommodate this situation
and log null, not throw an error. The RollingFileAppender handles this fine.)
> AdoNetAppender errors when writing Asp.net item when Request object is null
> ---------------------------------------------------------------------------
>
> Key: LOG4NET-331
> URL: https://issues.apache.org/jira/browse/LOG4NET-331
> Project: Log4net
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 1.2.11
> Environment: Windows Server 2008 R2
> Reporter: Andy Smith
> Priority: Minor
>
> When using AdoNetAppender, with a conversion pattern of
> '%aspnet-request{REMOTE_ADDR}', and I attempt to write a log entry during the
> Application_Start event, it throws an error (internally) and stops working.
> The error refers to "...Request is not available in this context.." which
> makes sense because its only in the Application_Start event. However the
> appender should accommodate this situation and log null, not throw an error.
> The RollingFileAppender, for instance, handles this gracefully.
--
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
