Home → Bug Reports →

Cascade is opening too many connections for FTP on IIS

• Edit

cpayan

03 May, 2012 01:49 AM

The title kind of says it all, we've had issues with IIS refusing connections from Cascade during publish jobs. The server admins say that Cascade is not cleaning up after itself and leaving open connections, then opening new connections to the server for every new file. After a handful of connections are made, the server starts refusing them, and the publish job falls on its face.

Is there a solution for this? Otherwise, should I submit this to the ideas?

1. 1 Posted by Bradley Wagner on 03 May, 2012 03:31 AM

   

   Cascade should be opening new connections for each thread in the publish job (between 1 and 4) and for each Destination being published to and then re-using those open connections for files published to the same destination. It should also be calling "quit" on each FTP connection after it's finished.

   Can you:

   • Enable logging for the following class: com.hannonhill.cascade.model.publish.callback.TransmitCallbackImpl
   • Attempt to reproduce the problem with the smallest publish job possible that still causes this to happen
   • Attach the log file to this discussion.
   • Also, let us know:
     1. what you published- a file, folder, site, publish set
     2. to how many destinations
     3. the time when the publish job started
     4. the time when you noticed problems in IIS so we can look at that section of the log

   We can then trace through the log to see if there are any problems closing connections.

   • Edit

2. Support Staff 2 Posted by Tim on 09 Aug, 2012 03:08 PM

   

   Hi,

   I just wanted to make sure that you saw Bradley's comment above.

   Let us know if you are still having problems with this - and if so, please be sure to follow the steps Bradley mentions above so that we can investigate further.

   Thanks!

   • Edit

3. Tim closed this discussion on 04 Apr, 2013 02:35 PM.