We have run into very weird situation. Occasionally, we got MessageSizeExceededException when calling message.Complete() after processing the message. It doesn't happen every time, but reproduces regularly.
The message itself was sent and received just fine. Its size is 1562 bytes according to message.Size. The entire workflow is as follows:
Call to AcceptMessageSession() to accept the next session, call to ReceiveBatch (10) to receive the next batch of up to 10 messages. In this particular case only one message was received. The message is then consumed by reading its body via GetBody<Stream> (), then call Complete().
Complete() fails with:
System.Exception {Microsoft.ServiceBus.Messaging.MessageSizeExceededException}Message exceeds maximum message size..TrackingId:2e38309a-e493-4833-822e-25ef9a5bb292,
Timestamp:2/18/2014 8:16:44 PM
at Microsoft.ServiceBus.Common.ExceptionDispatcher.Throw(Exception exception)
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.RunSynchronously()
at Microsoft.ServiceBus.Messaging.MessageReceiver.OnComplete(TrackingContext trackingContext, IEnumerable`1 lockTokens, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.MessageReceiver.Complete(TrackingContext trackingContext, IEnumerable`1 lockTokens, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.MessageReceiver.Complete(IEnumerable`1 lockTokens, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.ReceiveContext.Complete()
at Microsoft.ServiceBus.Messaging.ReceiveContext.Complete()
at Microsoft.ServiceBus.Messaging.BrokeredMessage.Complete()
We are using Microsoft.ServiceBus 2.2.0.0 (from the WindowsAzure.ServiceBus.2.2.6.0 nuget package). The region is East US. Thanks.