I am evaluating the CUBA Platform as a replacement for Lightswitch and I have several clients that are using the Azure SQL database. When I started using Azure SQL, I remember that connection resilience was added to Lightswitch and the underlying Entity Framework given Azure SQL will time-out connections. Discussions here.aspx) and here.
I did a partial port one of my less complex apps and noticed that the jTDS jdbc driver’s socket is getting closed periodically (Either by a timed out or network error) and manifests itself when a tab is closed or at other times in an edit screen. Unfortunately, the behavior is severe and in most cases requires the user to log out and log back in causing data to be discarded. I have verified running both in a Azure VM and in development.
I am wondering if you have seen this behavior? Looking at the stack trace, there are a LOT of third party libraries and I am not sure if this is even something you can fix. For me this does represent a problem as this renders the use of Azure SQL as a not a viable option when using the CUBA Platform as it stands now. This is going to be an issue for you more and more with the advent of Cloud based databases or any scenario where the database is not on the same LAN segment.
This is an awesome product and is will likely be my replacement for Lightswitch … you guys have done a great job!