1

I am using .NET RabbitMQ Client library. I want to develop a messaging system. For this, I have implemented all necessary methods of RabbitMQ. Moreover I have developed dispose() for deleting queue. I am calling this method in FormClosing event so this method will be triggered when user closes the application by clicking on close button and by the logic queue will be deleted. Up to this, all code is working perfectly.

But my problem is

I'm not able to delete a queue at the time of closing the application without clicking on close button (let's just say closing application from task manager or from command prompt using taskkill command or any abnormally reasons) as this dispose() will not be triggered. At this time, queue will not be deleted until I delete it from management portal manually.

So my question is,

How can I know that the application is closed and that orphan queue can be deleted?

Pritam
  • 685
  • 1
  • 14
  • 29

1 Answers1

3

RabbitMQ exposes a REST based management API which enables you to handle queue creation / deletion.

What you could do is have your application query that management API on startup to see if any queues were left abandoned because of previous unexpected shutdown, or you could have a completely different service which is responsible to do that (it's a design choice).

You can query your management API via EasyNetQ Management API:

managementClient.DeleteQueue(queue);

You can find the full documentation here.

Edit:

After doing some reading, perhaps an Exclusive or Auto-Delete queue will suffice?

Exclusive (used by only one connection and the queue will be deleted when that connection closes)

Auto-delete (queue is deleted when last consumer unsubscribes)

Community
  • 1
  • 1
Yuval Itzchakov
  • 146,575
  • 32
  • 257
  • 321
  • 1
    Thanks for your reply. I am creating all queues dynamically. so i will not know which queues are left orphan and which are not. I need to do implement this when object of RabbitMQ will go out of it's scope. Again thanks for your help and efforts. – Pritam Jan 17 '15 at 09:11
  • Why not keep track of the queues you create so you can check them at a later time? – Yuval Itzchakov Jan 17 '15 at 11:18
  • It increases the overhead of client. So i am not allowed to keep track. – Pritam Jan 17 '15 at 11:22
  • Yes it worked. Thanks. It removes queue but connection remains open. Now not able to close connection. I am not allowed to call dispose() at formClosing because it's not good practice. – Pritam Jan 19 '15 at 04:39