Hi everyone,
We’ve just released NServiceBus.MessagingBridge 3.0.1.
Fixed bugs
- #456 Bridged messages cannot be handled by older MSMQ endpoints
How to know if you are affected
You are affected if you are bridging MSMQ endpoints using Particular/NServiceBus.MessagingBridge 3.0.0
Symptoms
Bridged MSMQ messages cannot be handled by endpoints. The messages are moved to the error queue and the endpoints log a warning similar to:
2024-05-24 09:50:35.097 WARN Message '7e47b130-25e6-4b43-baf0-2339b773687a\105607' has corrupted headers
System.InvalidOperationException: There is an error in XML document (1, 1). ---> System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderList1.Read3_ArrayOfHeaderInfo()
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
at NServiceBus.Transport.Msmq.MsmqUtilities.DeserializeMessageHeaders(Message m)
at NServiceBus.Transport.Msmq.MsmqUtilities.ExtractHeaders(Message msmqMessage)
When to upgrade
You should upgrade immediately if you are affected by the bug. Otherwise, you should upgrade during your next maintenance window.
Where to get it
You can install NServiceBus.MessagingBridge 3.0.1 from NuGet.
With thanks,
The team in Particular
Please read our release policy for more details.