-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lost messages when using RabbitMQ transport #56
Comments
Ok I checked a bit more on the code level. It seems the service-bus.ts tries to handle the message.
And even if there is no handler registered for that message it still tries to read the message, forward it to no existing handlers (in this node) and then delete the message. Am I missing something? In NServiceBus there would be named endpoints and commands would go to exactly that endpoint with the name. Others would not read this message. |
Ok - found it. I need to use a different queue name in the I will continue further but maybe there could be more documentation or some step-by-step guide or example project on how to setup distributed messaging :-) |
Hi @Zehelein, You beat me to it :) By the look of the initial implementation, both the frontend and backend services were connected and reading from the same queue. The reason why messages were disappearing is that when the frontend service read a message first, it would discard it immediately as it didn't have any registered handlers for it. I agree that documentation could be improved regarding the integration of all the different components. I'll add a task to help improve that. Thanks for the feedback |
Thanks for looking into it and your fast follow up! 😃 |
Hi,
I am building a spike solution based on the NServiceBus tutorial https://docs.particular.net/tutorials/nservicebus-step-by-step/1-getting-started/ to see how to build it with your library.
I managed to get to step three to have two services - one "client ui" one to send a command and a "sales" endpoint to receive it. This works - the command is sent and it is also received. But every few messages
I added a bit of simple log output that shows up like that:
The second endpoint logs the received message - and the e86d... one is missing:
Do you have an idea what could potentially be the issue? I uploaded my current super simple solution here if that helps: https://github.com/Zehelein/service-bus-spike
And if I start up the client-ui without first starting the consumer (= sales) application first I get the rejected messages all of the time:
The text was updated successfully, but these errors were encountered: