Amjad Khoja (JIRA | 30 Jun 09:15

[jira] Created: (LOG4NET-162) It stops writing to the log file after certain threads are terminated and recreated.

It stops writing to the log file after certain threads are terminated and recreated.
------------------------------------------------------------------------------------

                 Key: LOG4NET-162
                 URL: https://issues.apache.org/jira/browse/LOG4NET-162
             Project: Log4net
          Issue Type: Bug
    Affects Versions: 1.2.10
         Environment: C#, .net framework 3.0, VS2005, Windows XP, intel pentium 4, 3 GHz, 1 GB RAM
            Reporter: Amjad Khoja
            Priority: Blocker

We are using log4net in an windows service application, which spans number of threads. Logging works
perfect until we try to refresh the cache where we terminate the threads and recreate it and in between the
logging stops. When debug we see that it goes to the logger print message statement and there is no error but
nothing gets written to the log file.

This behaviour is undpredictable as sometimes it works fine when it goes through the complete refresh method.

Settings of Log4net in app.config is as follow.

<log4net>
    <appender name="ErrorAppender" type="log4net.Appender.RollingFileAppender">
      <file value="C:\\ErrorNRTRDELogs\\NRTRDELogVPMNC.txt" />
      <appendToFile value="true" />
      <rollingStyle value="Size" />
      <maxSizeRollBackups value="10" />
      <maximumFileSize value="10MB" />
      <staticLogFileName value="true" />
      <layout type="log4net.Layout.PatternLayout">
(Continue reading)

Ron Grabowski (JIRA | 30 Jun 13:55

[jira] Updated: (LOG4NET-162) It stops writing to the log file after certain threads are terminated and recreated.


     [
https://issues.apache.org/jira/browse/LOG4NET-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Grabowski updated LOG4NET-162:
----------------------------------

    Priority: Critical  (was: Blocker)

> It stops writing to the log file after certain threads are terminated and recreated.
> ------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-162
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-162
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.10
>         Environment: C#, .net framework 3.0, VS2005, Windows XP, intel pentium 4, 3 GHz, 1 GB RAM
>            Reporter: Amjad Khoja
>            Priority: Critical
>   Original Estimate: 0.17h
>  Remaining Estimate: 0.17h
>
> We are using log4net in an windows service application, which spans number of threads. Logging works
perfect until we try to refresh the cache where we terminate the threads and recreate it and in between the
logging stops. When debug we see that it goes to the logger print message statement and there is no error but
nothing gets written to the log file.
> This behaviour is undpredictable as sometimes it works fine when it goes through the complete refresh method.
> Settings of Log4net in app.config is as follow.
> <log4net>
(Continue reading)

Ron Grabowski (JIRA | 30 Jun 13:55

[jira] Commented: (LOG4NET-162) It stops writing to the log file after certain threads are terminated and recreated.


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

Ron Grabowski commented on LOG4NET-162:
---------------------------------------

Have you enabled internal log4net debugging? What do those logs look like when the logging stops?

> It stops writing to the log file after certain threads are terminated and recreated.
> ------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-162
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-162
>             Project: Log4net
>          Issue Type: Bug
>    Affects Versions: 1.2.10
>         Environment: C#, .net framework 3.0, VS2005, Windows XP, intel pentium 4, 3 GHz, 1 GB RAM
>            Reporter: Amjad Khoja
>            Priority: Blocker
>   Original Estimate: 0.17h
>  Remaining Estimate: 0.17h
>
> We are using log4net in an windows service application, which spans number of threads. Logging works
perfect until we try to refresh the cache where we terminate the threads and recreate it and in between the
logging stops. When debug we see that it goes to the logger print message statement and there is no error but
nothing gets written to the log file.
> This behaviour is undpredictable as sometimes it works fine when it goes through the complete refresh method.
> Settings of Log4net in app.config is as follow.
(Continue reading)


Gmane