Skip to main content

RabbitMQ–How to remove unacked messages–Part II

Yesterday I showed how to remove unacked messages from a RabbitMQ queue through the Management Portal. Today let us leave the Graphical User Interface behind and solve the same problem from the command line.

Through the command line

RabbitMQ has multiple command line tools available in the sbin folder. The one we need is rabbitmqctl.bat

Show queues with unacked connections like this.

rabbitmqctl list_queues name messages_unacknowledged

The output should be something like this:

VLM.eShopExample.Worker-Development 1
VLM.eShopExample.Worker-Production 0

We see that one queue has an unacked message. Let's find out the channel and associated connection that is causing the unacked message. 

rabbitmqctl list_channels connection messages_unacknowledged

This returns the following output:

<rabbit@SERVER.1650192371.27249.9> 1

Ok, we found the channel that caused the problem. Let's close it. We specify the connection and a message that will be shown to the user.

rabbitmqctl close_connection "<rabbit@SERVER.1650192371.27249.9
>" "Sorry! We're closed."

We can remove the unacked message from the queue by purging it with the following command:

rabbitmqctl purge_queue VLM.eShopExample.Worker-Development

Let's run the first command again to verify that we no longer have any unacked messages.

rabbitmqctl list_queues name messages_unacknowledged
VLM.eShopExample.Worker-Development 0
VLM.eShopExample.Worker-Production 0
Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more