Hi,
I tried to use archiving (DateAndSequence) in combination with async target and keepFileOpen.
Testing this feature locally with our database log worked fine and the archive files where created like expected (Database 20161205.1.log, Database 20161205.2.log ....).
Putting same configuration under stress running multiple WCF-Requests causing the logging to stop. Leaving a valid log file like Database ${522or5ae}.0.log and no further activity.
First I thought it could be something like #1029 but updating from 3.2.0 to 4.3.11 did not help. It looks like the logger dies silently the very moment the current file is archived (see internal log).
The WCF Service is running on Windows Server 2008 and .Net-Framework 4.5.1.
My current work around is using the archiving on daily base only. but files with size of 1.5 GB and more are not easy to handle.
nlog.config.txt
nlog-internal.log.txt
Hi,
I tried to use archiving (DateAndSequence) in combination with async target and keepFileOpen.
Testing this feature locally with our database log worked fine and the archive files where created like expected (Database 20161205.1.log, Database 20161205.2.log ....).
Putting same configuration under stress running multiple WCF-Requests causing the logging to stop. Leaving a valid log file like Database ${522or5ae}.0.log and no further activity.
First I thought it could be something like #1029 but updating from 3.2.0 to 4.3.11 did not help. It looks like the logger dies silently the very moment the current file is archived (see internal log).
The WCF Service is running on Windows Server 2008 and .Net-Framework 4.5.1.
My current work around is using the archiving on daily base only. but files with size of 1.5 GB and more are not easy to handle.
nlog.config.txt
nlog-internal.log.txt