You are on page 1of 4

WCF binding – Understanding and configuring buffer management

Developing or consuming service-oriented applications? Ever came across HTTP
400’s? …a needless question though. It is not uncommon to find a WCF
CommunicationException with HTTP 400 (Bad Request). Quite a few of these
instances may happen to be returning an error message that would say – “ The
maximum message size quota for incoming messages (65536) has been exceeded. To increase
the quota, use the MaxReceivedMessageSize property on the appropriate binding element ”.
In certain complex project architectures, you may not get to see the detailed
error message, especially, if you are just working on the UI end of it.
To find out a solution for this, let us understand how WCF does the buffer
Background & Solution:
In the simplest form, a buffer is a chunk of memory and buffer pool is a set of
one or more buffers.
It all starts when the BufferManager is created. BufferManager creates and
manages the buffers and buffer pools, depending on the values that you set in
the binding configuration in the application’s config file. Let’s first see what those
buffer-related values are.
MaxBufferPoolSize is the size of the largest buffer pool that the BufferManager
can manage.

If, in case, allocating buffer to an incoming message would mean that it
would exceed this limit, then, the message would take a new buffer out
of the heap and the garbage collector takes care of it once used up.
If this value is 0(zero), it means that each request would take a new
buffer out of the memory heap and will be taken care of, by the
garbage collector.

MaxBufferSize is the size of the largest individual buffer that the buffer manager
can allocate (to any buffer pool).

For streamed transfers, only the SOAP headers need to be buffered while
the message body can be streamed on-demand. In such cases, this would
just mean the maximum size of the SOAP headers. For buffered transfers,
it is the maximum size of the headers and message body.

MaxReceivedMessageSize is the maximum size of a message that can be
received on a channel.

the BufferManager would create 3 pools as – 1st pool that holds buffers of size 128 bytes each 2nd pool that holds buffers of size 256 bytes each 3rd pool that holds buffers of size 450 bytes (this pool should otherwise hold buffers of size 512. They are only allocated when a message arrives to be processed. For buffered transfers. It is equal to the MaxBufferPoolSize / buffer size that pool can hold. the MaxBufferPoolSize for the example is 1800. For streamed transfers. it would limit it to 450) Here is a logical depiction of the buffer pools from above example. When? Buffers are not allocated when the pools are created. The ‘n’ below represents the number of buffers each pool can hold. though the sizes of the buffers being held by each of those differ. For example. this is the same as the MaxBufferSize. this is either greater than or equal to MaxBufferSize (for obvious reasons mentioned above) How? When the BufferManager is created. 1. with each pool holding up to a memory determined by MaxBufferPoolSize. Request arrives . if the MaxBufferSize is set to 450 bytes. until it reaches the maximum allowed message size (as set by MaxBufferSize). Say. 4501 2561 1281 1282 1283 128n 1284 n=>1800/128 =14 =4 4502 2562 2563 256n 4503 2564 n=>1800/256 =7 450n 4504 n=>1800/450 Note that each buffer pool’s maximum size is the same. but since the MaxBufferSize is lesser than 512. The buffers in each of these pools would have sizes in an incremental pattern of the multiples of 128. a series of buffer pools are also created.

using too much memory would also decrement performance. the pool’s size exceeds the MaxBufferPoolSize. the buffer manager tries to put the buffer that held the message back into its pool for reuse. let us see a sample configuration setting w. normally has ‘n’ number of concurrent requests. if your server. If the message size is more than the MaxBufferSize. the message is allocated a buffer out of the heap (not managed by BufferManager). you should find a balance between time and memory. 4. Once processed.t. However. Otherwise. the buffer will not be returned back to the pool. the settings we defined in the What? Section of this post. But. <binding name="WSHttpBinding_SampleFeedService" closeTimeout="00:00:30" openTimeout="00:00:30" receiveTimeout="00:00:30" sendTimeout="00:00:30" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="524288" maxReceivedMessageSize="2097152" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false"> <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" /> <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false" /> <security mode="None"> <transport clientCredentialType="Windows" proxyCredentialType="None" realm="" /> <message clientCredentialType="Windows" negotiateServiceCredential="true" establishSecurityContext="true" /> </security> </binding> .e. then you may have to set the MaxBufferPoolSize as ‘n’ times the MaxBufferSize. it is allocated an unmanaged buffer. on the memory heap i. if by doing so. the message gets processed. buffer that is garbage collected as when it is available for collection.2.r.. As a developer. 5. If appropriate pool is identified with available buffers. Also. Trade-off If you need to process large messages. BufferManager tries to find a pool that can hold buffers that are sufficient for this message 3. Example configuration Finally. you can use a large MaxBufferSize. As a thumb rule.