Skip to main content

Service Bus Queues from Windows Azure - Death letter and poison messages

I will continue the series of posts about Service Bus Queues. In this post we will talk about death letter. First of all, this concept is common to Service Bus and is not specific only to Service Bus Queues.
We should imagine death letter as an internal queue in our queue where all the messages that cannot be processes are added. This kind of messages is called death messages. For example what is happening in the following situation with the message that is abandoned:
BrokeredMessage message = qc.Receive();
try
{
if (messsage !=null)
{
    ...
    message.Complete();
}
catch(Exception ex)
{
    message.Abandon();
}
We will have a message that hangs on the queue and will be consumers over and over again without success. In this case we would need a method to mark the message as invalid. One solution is to invalidate the message and write this to a log. In this case even if the message is invalid we call the Complete() method. Be very careful when you call the Abandon() method. The message will be available in the queue again – it is very easy to create in this way messages that hang on the queue and cannot be processes.
Other option is to mark the message as “Differ”. In this case we will remain in the queue but we will be able to access it only by the message ID. This is not a valid case for our discussion.
Another solution is to mark the message as a poison message. A message marks as poison will be putted as a death letter.
message. DeadLetter()
or
message. DeadLetter(“…”,”…”)
In this way we mark the message as dead letter. The message is moved to death letter queue.
This sub-queue can be consumed by any other system or consumer and check the messages, log them and so on. The only thing that is not possible to do with it is to add the message to the original queue. To be an able to do this we will need to create a new BrokeredMessage with the same content. As a hint, the name of the sub-queue is [queueName]/$ DeadLetterQueue.
To be able to consume messages from this sub-queue we need to get the name of death letter queue. This can be very easy obtained using the FormatDeadLetterPath method of the QueueClient. After this step we obtained a normal QueueClient that can be used as we know it.
QueueClient deadletterQC = factory.CreateQueueClient(deadLetterQueuePath);
…
var message = deadletterQC.Receive();
…
We are not the only one that can put the messages in death letter queue. Windows Azure can mark a message from the queue as death when:
  • Message expired (TTL)
  • The maxim delivery count for a message is exceed
In this post we saw when is good to use death letter messages from Service Bus Queues. This type of messages can help us to decrease the complexity of our project. For example it is very simple to write a consumer that try for 3 times to process a message and if the action is without success to throw the message in the death letter queue.

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…