4.2 beta 7, Bug: Blocked sync server causes exception

Currently I'm blocking access to sync.logos.com (I'm not paranoid about privacy, I just need a clean installation). In the logs, I'm getting the following:

2010-11-18 21:39:27.9407    12    Info    SyncManager    (Timed) Uploading 100 items.
2010-11-18 21:39:29.0088    12    Info    SyncManager    (1064ms) Uploading 100 items.
2010-11-18 21:39:29.0088    12    Warn    SyncManager    Error occurred during synchronization upload - Libronix.DigitalLibrary.Synchronization.SyncClientException: Unhandled exception during synchronization. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:443
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at Libronix.DigitalLibrary.Synchronization.SyncClient.SubmitRequest(SyndicationFeed syndicationFeed, Nullable`1 dtSince, Nullable`1 dtSinceCollaborating, IEnumerable`1 headers, Boolean bExcludeDeleted)
   at Libronix.DigitalLibrary.Synchronization.SyncClient.UpdateItems(IEnumerable`1 seqTupleSyncItems)
   --- End of inner exception stack trace ---
   at Libronix.DigitalLibrary.Synchronization.SyncClient.UpdateItems(IEnumerable`1 seqTupleSyncItems)
   at Libronix.DigitalLibrary.Synchronization.SyncManager.TryUploadItems(ISyncClient syncClient, IDictionary`2 dictItemSources, List`1 listSuccessfulBatchSyncDates)

Obviously the operation should fail, but it shouldn't generate an exception. And neither should it try as often as it is doing. If the server is down, it doesn't need to retry every few seconds.

I tried opening port 443 on my local apache installation to see if I could get a fail rather than an exception, but it didn't work (though the error message is different).

Find more posts tagged with

Comments

Melissa Snyder

Mark ~ I've submitted your report. Thanks.

Update: Per development, the .NET Framework throws exceptions when an operation fails by design and there isn't a way to avoid it. The log file is slightly inaccurate in saying that it's an "unhandled exception" because it is actually getting handled.

It retries every few seconds to see if the server is back up as we want to restore sync functionality as soon as possible. In the case of a real server failure, this is what we would want it to do.

JimTowler

https://community.logos.com/discussion/comment/193914#Comment_193914

Please FIX this crash!!!

Blocking the SYNC of this product is a valid thing for a user to need or want. The application should not crash. It did not use to crash.

Crashing is NOT acceptable for this "error".

Mark Barnes

https://community.logos.com/discussion/comment/194074#Comment_194074

The application should not crash. It did not use to crash.
Crashing is NOT acceptable for this "error".

It doesn't crash. It just silently writes an unhandled exception error to the log. Annoying, but that's all.

JimTowler

https://community.logos.com/discussion/comment/194088#Comment_194088

Thanks Mark.
A one-liner error or status would be nicer, but at least no crashing then.
I still can't believe that Sync does not back-off a little when it fails. But never mind ...

Rosie Perera

https://community.logos.com/discussion/comment/193914#Comment_193914

It retries every few seconds to see if the server is back up as we want to restore sync functionality as soon as possible.

It should not retry every few seconds. Every couple of minutes should be sufficient. <edit> Most autosave features don't save more often than that. </edit> It slows down everything when it keeps trying over and over like that.