You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Dominik Psenner (JIRA)" <ji...@apache.org> on 2014/10/01 13:25:33 UTC

[jira] [Commented] (LOG4NET-442) ReconnectOnError

    [ https://issues.apache.org/jira/browse/LOG4NET-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154672#comment-14154672 ] 

Dominik Psenner commented on LOG4NET-442:
-----------------------------------------

The appender failed to connect to the sql server when trying to send the buffer. I would expect the appender to discard the events and only retry to connect when the next events come in. So the question is: have you "created" some log events after that the server was turned on again and was running successfully? Powering the server up might take some time and you will have to consider to wait for that time to pass by.

> 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)