I have a VB.NET app that runs through the job scheduler on a Win2k server. The app is essentially shepherding xml files from one ftp site to another to support a series of interfaces between various other applications. It wakes up every 20 seconds and checks a dozen or so ftp sites for specific file names. If it finds something, it ftp's it to the local server for archiving, then opens connections to one or more (typically three) other servers and transfers the file to them. Not particularly high volume, probably processing 100-200 files a day.
My problem is that over time (a period of hours, not days) I see the application start to slow down and use excessive amounts of cpu. I am declaring my FTPClient locally in a subroutine, and using the quit() method to close things out when I am done with it. I have to assume that my issue is ftp related, as I have related apps that run on the same server and using the same resources except the edtftpnet dll, and they are not having any performance issues. If I stop the scheduled job and the restart it, performance is very good until the job runs for a few more hours, but gradually deteriorates again.
I am trying to determine if this is an application issue on my end, an issue with edtftpnet, or simply an ftp 'feature' (the dread connection TIME_WAIT, etc.). Anybody have any ideas? I would be happy to post my code if it would help.
I see that there is a later version of the dll available (I am using 1.1.5). Are there enhancements in the later version that may resolve my issue?
Thanks.
