We’ve just released NServiceBus.SqlServer 6.3.3.
#954 Messages may be lost in cases of database connectivity problems
You are affected if you are using Azure SQL.
Messages are removed from the queue but no handler is executed and no audit information is captured—the messages are lost without a trace.
This occurs when there are either transient connectivity problems between endpoints and the transport database or there is high SQL instance resource usage. In these scenarios, you may see the following log messages:
WARN - Sql peek operation failed
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. —> System.ComponentModel.Win32Exception: The wait operation timed out
WARN - Sql receive operation failed
System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. —System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
You should upgrade immediately if you are using Azure SQL.
You can install the new version of NServiceBus.SqlServer from NuGet.
The team in Particular
Please read our release policy for more details.