You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subscribing to MessageFailed events from ServiceControl.Contracts does not include the message body, even though the message is text, less than 85KB (small enough to avoid the Large Object Heap), and Full-Text indexing of message bodies is enabled.
Who's affected
Anyone subscribing to ServiceControl.Contracts MessageFailed event and trying to access the message body when using ServiceControl 5.0 or later.
Root cause
The transition to RavenDB 5 required changes in how the message body is stored in ServiceControl which were not reflected by matching changes to the code publishing external integration events.
awright18
changed the title
MessageFailed Integration events do not contain message bodies
ServiceControl MessageFailed events do not contain message bodies
Sep 26, 2024
Symptoms
Subscribing to
MessageFailed
events from ServiceControl.Contracts does not include the message body, even though the message is text, less than 85KB (small enough to avoid the Large Object Heap), and Full-Text indexing of message bodies is enabled.Who's affected
Anyone subscribing to ServiceControl.Contracts
MessageFailed
event and trying to access the message body when using ServiceControl 5.0 or later.Root cause
The transition to RavenDB 5 required changes in how the message body is stored in ServiceControl which were not reflected by matching changes to the code publishing external integration events.
Original report
Describe the bug
Description
When subscribing to ServiceControl events the MessageFailed events do not contain message bodies.
Expected behavior
MessageFailed events contain message bodies.
Actual behavior
MessageFailed events do not contain message bodies.
Versions
Please list the version of the relevant packages or applications in which the bug exists.
It was identified in 5.9 but is likely a problem in all 5.x versions.
Steps to reproduce
Follow the steps in subscribing to ServiceControl events in order to received failed messages
Throw an exception when handling a message in a message handler that is connected to ServiceControl
Relevant log output
No response
Additional Information
Workarounds
Possible solutions
Additional information
The text was updated successfully, but these errors were encountered: