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

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

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more