[
https://issues.apache.org/jira/browse/LOG4NET-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157938#comment-14157938
]
Dominik Psenner edited comment on LOG4NET-442 at 10/3/14 12:40 PM:
-------------------------------------------------------------------
I'm afraid this might be a new "feature" of .NET framework 4.5.1:
http://blogs.msdn.com/b/dotnet/archive/2013/06/26/announcing-the-net-framework-4-5-1-preview.aspx
{quote}ADO.NET connection resiliency is a great answer to these connection
scenarios. It is able to *re-connect an app to the database* and replay session
state transparently *when* an app’s *database connection is broken*.{quote}
was (Author: nachbarslumpi):
I'm afraid this might be a new "feature" of .NET framework 5.1:
http://blogs.msdn.com/b/dotnet/archive/2013/06/26/announcing-the-net-framework-4-5-1-preview.aspx
{quote}ADO.NET connection resiliency is a great answer to these connection
scenarios. It is able to *re-connect an app to the database* and replay session
state transparently *when* an app’s *database connection is broken*.{quote}
> 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)
