[
https://issues.apache.org/jira/browse/LOG4NET-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157045#comment-14157045
]
Dominik Psenner commented on LOG4NET-442:
-----------------------------------------
Alright, can you share the last nights debug log? It would be awesome if you
were able to run log4net from source and attach a debugger to see if
m_dbConnection.State still reports "Open" even if the connection is lost. My
current assumption is that this is an issue of the database connection provider
you are using.
> 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
> 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)
