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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP