Nest.js has trouble connecting to RabbitMQ with latest amqp-connection-manager

Hey nest.js folks!

I’m the maintainer of amqp-connection-manager. I’ve been making some attempts to modernize the code in this library lately - many years ago it was originally written in CoffeeScript, then migrated to JavaScript. Recently I merged a number of fixes from contributors, and I migrated the whole codebase to typescript.

The typescript migration happened between 3.3.0 and 3.4.0, and somehow this specific release is causing some problems for some nest.js users. They’re seeing:

Error: Channel closed by server: 406 (PRECONDITION-FAILED) with message "PRECONDITION_FAILED - fast reply consumer does not exist"

This is a weird error - usually this would be caused by someone trying to post a message with a replyTo: 'amq.rabbitmq.reply-to' before setting up a consumer listening on that queue (as per this). This sounds like a bug outside of amqp-connection-manager… except all the users claim they can reliably get this to work with 3.3.0 and not with 3.4.0. The changes I made between 3.3.0 and 3.4.0 are pretty mild, and I don’t see how any of them could be somehow causing this error (although, clearly something has changed). Doubly unfortunately, while lots of users are running into this problem, if I try this demo repo it works fine, and no one has been able to generate a minimal test case that reproduces this.

Since I’m not a nest.js user, I’m reaching out to see if anyone familiar with the nest.js RabbitMQ transport has any clever ideas about what could be could be causing this problem or thoughts about ways to recreate it. (I’m essentially grasping at straws here. -_-)

Thanks in advance!