Why does FS LIST COPYREQUESTS show a copy request in progress on the destination machine that has already failed with a RC 22?
If a FS COPY request fails due to a network problem such as with RC: 22 and Result: “STAFConnectionWrite: Error writing to socket: send() RC=10054: 22”, it’s possible that half of the connection on the destination (“TO”) machine side didn’t get closed. So, it still shows up in the FS LIST COPYREQUESTS LONG request on the destination machine (even though the copy request is no longer running) and it causes RC 19 if you resubmit this FS COPY request. This occurs because the network connection on the FS COPY destination machine may not be notified if the other side of the network connection ended unless keepalive is enabled and the KeepAliveTime has expired. Note that on Windows, keepalive is not enabled on a Windows socket by default. Keep Alive refers to the time before TCP will begin sending keepalive messages, but only if keepalive is enabled for a network connection. The default is usually around 2 hours. KeepAliveInterval is the time between retransmissions of keepalives once a Keep
