Home Dashboard Directory Help
Search

NotifyFilters.Size does not raise events on Server 2008 R2/Windows 7 by mabra99


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Bug
ID: 777417
Opened: 1/24/2013 9:37:45 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Hello !

I have a app running for several years and I am on the way to use this on Server 2008.
This app monitors >>10.000 's of logfiles per day of a big number of business applications
and runs 24x7 and notifies the admin crew about importent errors and/or failed transactions.
This app is an importent piece in the business infrastructure.

The app is net [C#] and uses the Framework 2.0 and inside, the FileSystemWatcher [FSW]
is the power horse. This worked well even with a huge number of files and more then
~10^6 events per day.

Running on Server 2008 (R2) and we have less events. I tracked this down to be a problem
of NotifyFilters.Size.

Many files are continued to work, but many other not, and I am stuck to migrate this
app to a 2008 (R2) server. There are different patterns in behavior, which write the logfiles:

a) OpenAppend, write, close.
b) OpenAppend, write, sleep, write, sleep, write, close

a) Causes the FSW to raise events,
b) Events are only generated on the first write after open and on the final close.

This is in contrast to the behavior on Server 2003/XP, where NotifiFilters.Size
[pattern b) of above] raises the events on each update. So, if the app keeps
the logfile open for hours, but regularly appends textlines, no event at all is
raised.

Due to the lot of files and continous changes, polling is not an option.
I see this ether as a platform specific bug in the framework or in Server 2008.

There is no publicly seeable documentation, which point out a new behavioral
pattern of FSW.

So, I stuck here. The remaining option are not optimal: Downgrade to
Server 2003 [maintenance ends 2014] or migrate to Linux [which works
well, but integration in the Windows Landscape is suboptimal].

Hope, this is a bug and to get a fix.

Thanks you very much,

Manfred Braun
(mabra)
Details
Sign in to post a comment.
Posted by Microsoft on 2/21/2013 at 7:24 AM
Thank you for your feedback. We are not going to be able to address this issue in our next release due to other priorities.

Regards,
Immo Landwerth
.NET Framework team
Posted by Microsoft on 1/25/2013 at 2:01 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 1/24/2013 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
MS-Connect--FSW-Problem--Repro.zip 1/24/2013 12 KB