Skip to content
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

Native Message ID is not set based on NServiceBus.MessageId header causing incompatibility with native integrations #581

Open
kbaley opened this issue Jul 25, 2022 · 0 comments

Comments

@kbaley
Copy link
Contributor

kbaley commented Jul 25, 2022

This issue was transferred from a private repository

Users sometimes want to set the native message ID of the outgoing message for ASB which currently is initialized with a random guid. They are dealing with native integrations and do not want the receiver to be required using the NServiceBus.MessageId.

The comment in the code is:

// Cannot re-use MessageId to be compatible with ASB transport that could have native de-dup enabled

As the comment suggested, when native de-duplication is enabled, this causes problems, including message loss on second-level retries. ASB also provides access to the native message which users can use to promote it into the headers within a pipeline. However, for users that don't plan to ever use native de-deduplication, perhaps we can provide alternatives like a transport setting or a send option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant