What is the maximum size that maxReceivedMessageSize can be set to for a NetNamedPipeBinding?

Question

I noticed that 2147483647 seems to be a popular choice for maxReceivedMessageSize but is this the limit?

Ideology

On the other hand, you might want to consider that setting it to 2 GB of message size means your WCF server will potentially have to deal with several messages of up to 2 GB in size simultaneously - can it do that?? Marc – Cobber

It is if you have a 32bit server... – Olcott

Answer 1

Nope, the limit is Int64.MaxValue¹ which is: 9223372036854775807

Camara

In the web.config-File, only the Int32-limit seems to work. Maybe it's a parsing issue. – Orren

When setting this value through code I get ArgumentOutOfRange exception for this parameter. – Stargell

Answer 2

MaxMessageReceivedSize in basicHttpBinding appears to be an int32 - setting it over the max value of an int32 results in:

This factory buffers messages, so the message sizes must be in the range of an integer value. Parameter name: bindingElement.MaxReceivedMessageSize

Scabbard

Nope, it's Int64 (long): msdn.microsoft.com/en-us/library/… – Gaylord

Answer 3

MaxReceivedMessageSize and MaxBufferSize must same value and MaxBufferSize is Int32.

Saturniid

Not true - MaxBufferSize is only used if you are using Buffering. If you are using Streaming, then it is ignored. This is why MaxReceivedMessageSize is Int64 and can be different to MaxBufferSize. – Hoarse

Do you mean maxBufferPoolSize and maxReceivedMessageSize? – Paleoasiatic

BasicHttpBinding MaxBufferSize is Int32, but MaxReceivedMessageSize is Int64. msdn.microsoft.com/en-us/library/… – Gaylord