RMQ Every other request responds "There is no matching message handler defined in the remote service."
See original GitHub issueIs there an existing issue for this?
- I have searched the existing issues
Current behavior
Currently every other request works, and every other is being marked as “Unroutable (drop)” by RabbitMQ and responding with “There is no matching message handler defined in the remote service.”.
Minimum reproduction code
https://github.com/rittaschool/ritta-server
Steps to reproduce
./update.sh
docker-compose -f docker-compose.dev.yml up
- http://localhost:15672 -> guest:guest
- Create new users:
users:users
andauth:auth
- Restart (CTRL+C old process, run step 2)
- http://localhost:3000/docs
- /api/v1/users
- Run twice
Expected behavior
The list of users should be sent every time.
Package
- I don’t know. Or some 3rd-party package
-
@nestjs/common
-
@nestjs/core
-
@nestjs/microservices
-
@nestjs/platform-express
-
@nestjs/platform-fastify
-
@nestjs/platform-socket.io
-
@nestjs/platform-ws
-
@nestjs/testing
-
@nestjs/websockets
- Other (see below)
Other package
No response
NestJS version
8.2.4
Packages versions
[System Information]
OS Version : Linux 5.15
NodeJS Version : v16.13.1
YARN Version : 3.0.2
[Nest CLI]
Nest CLI Version : 8.1.6
[Nest Platform Information]
platform-express version : 8.2.4
platform-fastify version : 8.2.4
microservices version : 8.2.4
schematics version : 8.0.5
graphql version : 9.1.2
swagger version : 5.1.5
testing version : 8.2.4
common version : 8.2.4
config version : 1.1.6
core version : 8.2.4
cli version : 8.1.6
Node.js version
16.13.1
In which operating systems have you tested?
- macOS
- Windows
- Linux
Other
Authentication part of the application works fine without this problem. I am pretty sure that the problem lies somewhere inside the apps/users part of the repository.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
mqtt - Nestjs - There is no matching event handler defined in ...
I'm getting the same error message but it's happening randomly not every time while a call has been produced from origin service to...
Read more >NestJS microservices error with "No matching message handler"
For me it was an issue where I was importing a DTO from another microservice ... error: There is no matching message handler...
Read more >API with NestJS #19. Using RabbitMQ to communicate with ...
With a message queue, we can send a message from one service to another without knowing if it can handle it. Therefore, we...
Read more >Microservices | NestJS - A progressive Node.js framework
Nest abstracts the implementation details of each transporter behind a canonical interface for both request-response and event-based messaging. This makes it ...
Read more >Build Nest.js Microservices With RabbitMQ, MongoDB & Docker
In this video, we build a complete Nest.js microservices application using RabbitMQ as our distributed fault-tolerant message broker.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I found the answer from the Discord server!
The solution was to create a own queue for every microservice (and and a own event bus). https://github.com/rittaschool/ritta-server/commit/b837fd9f73a3d1163c02c2b5aef6102c5acb2334
Please, use our Discord channel (support) for such questions. We are using GitHub to track bugs, feature requests, and potential improvements.