golevelup / nestjs

A collection of badass modules and utilities to help you level up your NestJS applications 🚀

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Consuming From An Existing Durable Exchange

faruk-arslan opened this issue · comments

Hi, I'm trying to connect to an existing exchange and consume a queue. When I run my service, another exchange is created for the same topic and binded to it. All the routing key, queue name, exchange name params are same except the arguments. It does not use the existing one and creates a new exchange with no arguments. I already use durable: true for my exchange and queue config but yet still does not use it.
image
Eventually I need to use the existing exchange, with the durable: true option.
My config is like below:
@RabbitSubscribe({ queue: 'my-queue', exchange: 'my-exchange', routingKey: 'my-routing-key', queueOptions: { durable: true, }, errorHandler: ackErrorHandler, })
And for main.ts exchange config:
exchanges: [ { name: 'my-exchange', type: 'x-delayed-message', options: { durable: true, }, }, ]

Using the "@golevelup/nestjs-rabbitmq": "^3.6.0"

@WonderPanda can you help with this?

@faruk-arslan Hi, sorry for the late reply. Could you create a repro and post it here? That might be easier to just boot up and see what you're observing