DataContract Serialized Stream-Bodied Messages Sent in Repair and Submit Are Corrupted

[c-lombardi]

When re-queuing Dead-Letter-Queued messages with a Stream body that have a custom content type that was serialized by a Data-Contract-Serializer, the stream sent in the new message can no longer be read by the application that originally Data-Contract-Serialized the message.

Attempting to re-queue the same messages with ByteArray and String content types are also unsuccessfully able to be de-serialized by the application.

It appears that the message body is corrupted when the body was a custom content type and serialized with the DataContractSerializer.

[c-lombardi]

I think that you might just need to instantiate the new BrokeredMessage with the body of the old message as a stream:

BrokeredMessage newBrokeredMessage = new BrokeredMessage(deadLetteredMessage.GetBody<Stream>()) { SessionId = deadLetteredMessage.SessionId, ContentType = deadLetteredMessage.ContentType, CorrelationId = deadLetteredMessage.CorrelationId, ForcePersistence = deadLetteredMessage.ForcePersistence, Label = deadLetteredMessage.Label, MessageId = deadLetteredMessage.MessageId, PartitionKey = deadLetteredMessage.PartitionKey, ReplyTo = deadLetteredMessage.ReplyTo, ReplyToSessionId = deadLetteredMessage.ReplyToSessionId, ScheduledEnqueueTimeUtc = deadLetteredMessage.ScheduledEnqueueTimeUtc, TimeToLive = deadLetteredMessage.TimeToLive, To = deadLetteredMessage.To, ViaPartitionKey = deadLetteredMessage.ViaPartitionKey };

[paolosalvatori]

Hi @c-lombardi the Clone overloaded method in the BrokeredMessageExtensions class should do exactly what you are looking for. This is the first time that I receive this feedback. Could you please debug the application and see if the proper method overload is used when choosing Stream as format for the message to resubmit?

        public static BrokeredMessage Clone(this BrokeredMessage message, Stream stream)
        {
            if (stream == null)
            {
                return null;
            }
            if (stream.CanSeek)
            {
                stream.Seek(0, SeekOrigin.Begin);
            }
            var clone = message.Clone();
            BodyStreamPropertyInfo.SetValue(clone, stream);
            return clone;
        }

[c-lombardi]

I see what you are saying now and that seems to have resolved the problem for me in my local build!

[SeanFeldman]

seems to have resolved the problem for me in my local build!

Just making sure you're always using the latest release that can be obtained here.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.