Skip to main content

Service Bus Queues from Windows Azure - How to retry to consume messages and death letter

In the last blog post when I talked about poison messages that can exist in Service Bus Queues I told you how simple is to detect if a message was not processes with success for three times and throw him to the death letter sub-queue from Service Bus Queues. If you want to find more information about death letter please follow this link.
As a recap, each queue has a sub-queue where we can throw messages that were not processes – death letter. Service Bus automatically throw messages in this queue when the TTL expired, we reach the maxim limit of messages in a queue or when we don’t have enough space in the queue. The Service Bus is not the only one that can mark messages as death letter. We can do this also from the code and there are situations where is very useful.
Remarks: A messages that was marked as death letter cannot be added to the queue. We need to recreate it.
This is very useful when we try to process messages from a queue but because of an unknown cause we cannot process the messages with success. In this case if we use the Peer-Look Receive Mode and a message is not removed from the queue until we call the complete action, these messages will hang in the queue until TTL expired. In the same time, the consumers will try to process these messages over and over again. This is a waste of resources and there are some cases when a message cannot be processes first time but if after 3 attempts we could not process the messages than we should mark him as poison messages.
In the following example I defined a consumer that tries to consume messages from Service Bus Queues. For the messages that are the 3th time when the system try to process them without success they are marked as death letters. Another system will process them letter on and can do more actions with them or only log it.
 QueueClient qc =
    QueueClient.CreateFromConnectionString(
    myFooConnectionString, "FooQueue");
while(true)
{
    BrokeredMessage message = qc.Receive();
    if(message == null)
    {
        Thread.Sleep(1000);
        continue;
    }
   
    try
    {
        // process our message.
        message.Complete()
    }
    catch(Exception ex)
    {   
            if( message.DeliveryCount > 3 )
            {
                message.DeadLetter();
            }
            message.Abandon();
    }
}
In this code sample the key is DeliveryCount. This is a property of a BrokeredMessage that is automatically incremented when someone retrieves the message from Service Bus Queue. When this value reach 3 then we mark the message as dead letter and we will not be able to access it from the queue.
In the following code sample I will retrieve all the messages that were marked as death letter.
QueueClient qcdl =
    QueueClient.CreateFromConnectionString(
    myFooConnectionString, QueueClient.FormatDeadLetterPath("FooQueue"));
while(true)
{
    BrokeredMessage message = qcdl.Receive();
    if(message == null)
    {
        Thread.Sleep(1000);
        continue;
    }

    // Process message.
}
Notified how I get the name of the queue where I stored the deferral messages? QueueClient.FormatDeadLetterPath("FooQueue") – don’t forget about this helper functions that framework offer to us.
In this post we saw how we can mark messages as deferral when we try for 3 types to process them without success.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…