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.
Enable logging for the following class:
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:
what you published- a file, folder, site, publish set
to how many destinations
the time when the publish job started
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.