-
Notifications
You must be signed in to change notification settings - Fork 47
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
Poison messages are moved to Error Queue #853
Comments
I have done a bit more analysis and this is not entirely correct. |
@boblangley can u check ASB and ASQ, for NSB v5 |
In ASQ (core v6) we do exactly the same. If the wrapper, which contains headers, can't be deserialized it's moved directly to the error queue. |
Symptoms
When a transport deems a message poison,
The message is forwarded to the error queue, the issue is that this message does not have all the headers a normal error has:
As it currently stands ServiceControl fails to import those messages:
Who's Affected
Users that are running ServiceControl v1.25.0 or below and are on NServiceBus v6
The text was updated successfully, but these errors were encountered: