Skip to content

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

@pabermod

Description

@pabermod

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions