WatchDirectory home page
WatchDirectory Startseite (Deutsche Version)
Site WatchDirectory (Français)
  Welcome, Guest. Please Login or Register
YaBB - Yet another Bulletin Board
   
  HomeHelpSearchLoginRegister  
 
Page Index Toggle Pages: 1
File transmission delay (Read 66 times)
allan
YaBB Newbies
*
Offline



Posts: 12
File transmission delay
Oct 26th, 2017 at 5:27pm
 
Hello,

I've ran into an issue a few times where a file is written to a folder but WatchDirectory has a delayed reaction to it. 
I current have a Run Multiple Sub Task setup
  • Fast Method

  • Events - FILENEW and FILECNHG

  • Run as a Windows Service


I also have several other tasks setup in the same fashion, all other feeds reacted to the file when it was created.

How can I further dig into the system to figure out why delay?

I can't seem to upload images:
With this file log1.PNG (21 KB) you exceeds the maximum allowed upload-directory volume.
Back to top
 
 
IP Logged
 
Gert
YaBB Administrator
*****
Offline



Posts: 2233
The Netherlands
Re: File transmission delay
Reply #1 - Oct 27th, 2017 at 10:07am
 
Hello Allan,

I am not sure what is happening, for that I would like to see your task.

Can you please:
Enable "debug"
Run the task
Wait until you see the delay again for a file
Stop the task and email (see below for my email) me a backup. Also tell me the name of the delayed file.
This blog has all the details: http://blog-en.gdpsoftware.com/2010/06/send-task-backup-to-support.html


I will look into the attachment issue.
Back to top
 

Gert Rijs - gert (at) gdpsoftware (dot) com
Blog: http://blog-en.gdpsoftware.com/
End Alzheimer's: http://www.alz.org&&...
WWW WWW GdPSoftware  
IP Logged
 
allan
YaBB Newbies
*
Offline



Posts: 12
Re: File transmission delay
Reply #2 - Oct 27th, 2017 at 2:28pm
 
Hi Gert,

I did eventually figure out what was happening.  I originally had debug information turned on for 1 sub-task but not the other 3, nor did I have FTP conversation enabled.  Well after I did turn on all of those options I analyzed the log and clearly saw that the issue was on the receiving server, and not ours or Watch Directories issue.

Basically the final task in my set is configured to move the file to a "processed" folder, the server it was connecting to would stall for 4-5 minutes before timing out which reset the WD task (connect and send file) which worked without timing out.  The side effect of waiting for the timeout meant the folder was accumulating more files to send but had to wait 4-5 minutes for the task to finish and kick off for the new file queued.  If another time-out period occurred, even more files got queued and delayed.

Ultimately I ended up created four separate tasks which monitored four directories, one for each end-point server.
Back to top
 
 
IP Logged
 
Page Index Toggle Pages: 1