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:

<[email protected]> 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 "<[email protected]
>" "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

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

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

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...
Read more
OSZAR »