Hi Andreas. Sure. The messages in question are used to generate Adobe pdf files. The message contains all the information in order to generate said documents and includes a fairly large amount of XML. The original message sent contains about 3.0 MB of XML and other various pieces of data. (I know that is a lot of data that could be compressed or turned into JSON but that is another discussion 
) When the Adobe server generates the document, it returns a byte array of roughly 500KB. which we stuff into the original message and pass it along to its next destination in the workflow. Before sending it onto the bus however, we check it size. So original message of 3MB of XML and other pieces of data + 500KB of byte[] data is less than 4MB. Serializing the entire message yields a size of roughly 3,523,650 of byte[] data. Because it is under 4MB limit, the databus property is not used, however when the message is sent using the context.Send() we get the following error:
System.Messaging.MessageQueueException: Insufficient resources to perform operation.
at System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransac
tion internalTransaction, MessageQueueTransactionType transactionType)
at System.Messaging.MessageQueue.Send(Object obj, String label, MessageQueueT
ransaction transaction, MessageQueueTransactionType transactionType)…
Just as a test… If I take the message contents and write it to the databus property and send the message it goes through the bus without any issues, In the Databus directory, I get a file that is 3.67 MB (which is still under 4MB). This whole thing is very vexing.
Thanks
-Len