It is not possible to distinguish between duplicated or no route in destination exchange #117

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.

Sign up for GitHub

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

Jump to bottom

Open

pabermod opened this issue May 6, 2025 · 0 comments

pabermod commented May 6, 2025 •

edited

Loading

In duplicate detection for exchanges,

When using publisher confirms if I have the following scenario:

Duplicate detection exchange MyExchange.MD with binding to the exchange MyExchange
Exchange MyExchange of type direct with no bindings

If the message cannot be routed in the destination exchange, we get the same message in the Return handler:

312 - NO_ROUTE

¿Can you change the error code or add a custom header when the problem is due to a duplicated message?

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment