[
https://issues.apache.org/jira/browse/LOG4NET-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589773#comment-14589773
]
Dominik Psenner commented on LOG4NET-442:
-----------------------------------------
The FAQ entry is a good step forward, can we do something about this in the
SendBuffer? I would actually like to drop the checks that fail to detect the
disconnection anyway and simply react on exceptions when sending the buffer
more or less like how Alessio Sanguineti pointed out in comment
https://issues.apache.org/jira/browse/LOG4NET-442?focusedCommentId=14157931&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14157931
.
> ReconnectOnError
> -----------------
>
> Key: LOG4NET-442
> URL: https://issues.apache.org/jira/browse/LOG4NET-442
> Project: Log4net
> Issue Type: Bug
> Components: Builds
> Affects Versions: 1.2.13
> Environment: Microsoft .NET 4.5.1
> Reporter: Alessio Sanguineti
> Attachments: log4net.txt
>
>
> Hello, in our .NET application using Log4Net to log on a Sql Server 2014
> database, we set the parameter "ReconnectOnError" to true in the ADO.Net
> Appender configuration.
> Even if the property seems to be read correctly (as visible on the log),
> whenever the server is not reachable for a while the appender does not
> reconnect anymore thus not logging anything else.
> We get the log file attached of a test where we turned off SQL Server for
> about 1 minute before restarting it.
> Thank you.
> Regards
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
