Service Bus 2.1 For Windows Server - TimeOutException on EndReceive Method

Question

I am using Service Bus 2.1 For Windows Server and I have a method to receive message asynchronously.

The body of my method is:

var waitTimeout = TimeSpan.FromSeconds(10);

        // Declare an action acting as a callback whenever a message arrives on a queue.
        AsyncCallback completeReceive = null;

        // Declare an action acting as a callback whenever a non-transient exception occurs while receiving or processing messages.
        Action<Exception> recoverReceive = null;

        // Declare an action responsible for the core operations in the message receive loop.
        Action receiveMessage = () =>
        {
            // Use a retry policy to execute the Receive action in an asynchronous and reliable fashion.
            retryPolicy.ExecuteAction(
                (cb) => messageReceiver.BeginReceive(waitTimeout, cb, null),
                (ar) =>
                    {
                        // Make sure we are not told to stop receiving while we were waiting for a new message.
                        if (!cts.IsCancellationRequested)
                        {
                            // Complete the asynchronous operation. This may throw an exception that will be handled internally by retry policy.
                            BrokeredMessage msg = messageReceiver.EndReceive(ar);

                            // Check if we actually received any messages.
                            if (msg != null)
                            {
                                // Make sure we are not told to stop receiving while we were waiting for a new message.
                                if (!cts.IsCancellationRequested)
                                {
                                    try
                                    {
                                        // Process the received message.
                                        processMessage(msg);

                                        // With PeekLock mode, we should mark the processed message as completed.
                                        if (messageReceiver.Mode == ReceiveMode.PeekLock)
                                        {
                                            // Mark brokered message as completed at which point it's removed from the queue.
                                            msg.SafeComplete();
                                        }
                                    }
                                    catch
                                    {
                                        // With PeekLock mode, we should mark the failed message as abandoned.
                                        if (messageReceiver.Mode == ReceiveMode.PeekLock)
                                        {
                                            // Abandons a brokered message. This will cause Service Bus to unlock the message and make it available 
                                            // to be received again, either by the same consumer or by another completing consumer.
                                            msg.SafeAbandon();
                                        }

                                        // Re-throw the exception so that we can report it in the fault handler.
                                        throw;
                                    }
                                    finally
                                    {
                                        // Ensure that any resources allocated by a BrokeredMessage instance are released.
                                        msg.Dispose();
                                    }
                                }
                                else
                                {
                                    // If we were told to stop processing, the current message needs to be unlocked and return back to the queue.
                                    if (messageReceiver.Mode == ReceiveMode.PeekLock)
                                    {
                                        msg.SafeAbandon();
                                    }
                                }
                            }
                        }

                        // Invoke a custom callback method to indicate that we have completed an iteration in the message receive loop.
                        completeReceive(ar);
                    },
                () =>
                    {

                    },
                (ex) =>
                {
                    // Invoke a custom action to indicate that we have encountered an exception and
                    // need further decision as to whether to continue receiving messages.
                    recoverReceive(ex);
                });
        };

        // Initialize a custom action acting as a callback whenever a message arrives on a queue.
        completeReceive = (ar) =>
        {
            if (!cts.IsCancellationRequested)
            {
                // Continue receiving and processing new messages until we are told to stop.
                receiveMessage();
            }
        };

        // Initialize a custom action acting as a callback whenever a non-transient exception occurs while receiving or processing messages.
        recoverReceive = (ex) =>
        {
            if (!cts.IsCancellationRequested)
            {
                // Continue receiving and processing new messages until we are told to stop regardless of any exceptions.
                receiveMessage();
            }
        };

        // Start receiving messages asynchronously.
        receiveMessage();

Since I have updated the dll Microsoft.ServiceBus to the version 2.1 (before I was using the version 1.8 and 2.0), I have every seconds two exceptions:

A first chance exception of type 'System.ServiceModel.FaultException`1' occurred in Microsoft.ServiceBus.dll A first chance exception of type 'System.TimeoutException' occurred in Microsoft.ServiceBus.dll

The methods who raises the exception are: The 'EndReceive' and Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.ThrowIfFaultMessage(Message wcfMessage)

I have seen some posts on internet but without any answer. Someone has already got this issue?

Answer 1

I had the same issue with version 2.05 of Servicebus library. I updated to 3.0 and it solved the problem.