Skip to main content
  • EN

Is there a reason why I get multiple notifications on a create topic when only one file is copied into the folder?

I have done some testing with a reasonably small file (8mb) and when copied I get a total of 17 notifications published to the topic that has been set up as a directory watch, as you can imagine if multiple files are copied I get some major notification spam.

I have noticed that there is a setting for 'Modify' (time to wait after modify) so that if multiple sequential notifications that are sent they can be ignored. Is there something like that for 'Create' that I am not aware of? I am really only looking for 1 notification for 1 file

I seem to be getting some unexpected results, has anyone else had success dealing with similar issues?

I have had success deploying the directory watcher subscription, my advise to you is to evaluate the behavior of the topic (by monitoring it) to define which test or sampling needs to take place to filter out the one signal you need.

If I remember correctly an intermediate dataset gathering the notifications can help to determine the following action.

https://knowledge.safe.com/articles/1402/fme-server-watch-publisher-tutorial-1.html

https://knowledge.safe.com/articles/31776/advanced-data-management-watch-publisher-2016.html

I'm sorry that this is happening. With 2016 and previous we have definitely seen duplicate messages coming from the Directory Watch publication on some systems. For 2017, we decided not to try and fix the current version, but instead we rewrote the Directory Watch to address this problem and improve the solution overall. We've done extensive testing on this new version and I'm confident this problem is gone. Unfortunately, for 2016 and previous I'm unsure of a workaround at this point. If you are using a local file system, try using a UNC path. We had two code bases for local and UNC path, which gave two different experiences. For 2017, we have a single approach and single experience for UNC and local paths.

I put in some logic to my workspace to test for "spam" notifications and only process the legitimate one. The workspace still gets triggered multiple times (fortunately for me 4-5, not 17) but takes less than a second to complete when it's a bad trigger.

yeah ok thanks for the answer @aaronkoning. I will be keen to get on 2017 when it comes out but will try the UNC path in the mean time.

Reply


Community Stats

30,353
Posts
115,361
Replies
38,091
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.