SSLSocket - EndReceive exception (wodSFTP / wodSFTP.NET / wodSFTPdll)

"A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied"

We have a Windows Service that periodically checks an FTP server for new files. Lately, we would receive notifications that the service stopped. After adding a few lines to catch any exceptions, I stumbled on this exception.

Thoughts as to what's causing it? It is pretty random and usually happens after hours in the weeeee hours of the morning.

I've modified the service to prevent it from completely shutting down, but I'd like to know if it is an issue on our side.

Thanks,

at WeOnlyDo.Net.Sockets.SSLSocket.EndReceive(IAsyncResult ar)
at WeOnlyDo.Net.Sockets.ProxySocket.EndReceive(IAsyncResult asyncResult)
at WeOnlyDo.Protocols.FTPplain.ReceiveNotification(IAsyncResult ar)

Daniel,

hi. This means that connection was broken when it wasn't supposed to be. Such as, if your modem has restarted, or similar. Usually wodSFTP would detect that silently, but if it cannot then it throws it to the application so it knows why disconnection occurs.

Are you using latest version of wodSFTP.NET? Can we somehow duplicate this issue?

Kreso

This happens irregularly and I cannot reproduce it except to leave the service running all night long with a breakpoint set.

We are using version: v1.7.6.214

Not sure if our licensing allows us to upgrade.

I put a work around in place and it is working so far. I am inquiring mainly because I wanted to know the underlying cause. Restarts and disconnects I do believe. Our FTP server is in Michigan and our data centers are still recovering from storms that happened earlier in the month.

Daniel,

only thing I can suggest is to catch that error and reconnect. Obviously connection is broken, so there's not much you could do just reconnect.

Anyway, let me know if problem persists and your workaround doesn't help.

Kreso