Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m getting the following communication exception for my wcf service making cal to another wcf service:
“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.”
I resolved this by increasing the size as below:
maxReceivedMessageSize=”50000000″
But, here I want to know whether any side effects of increasing message size to such big level.
Yes – it might. The reason WCF keeps this limit low (64K) by default is this: imagine your server is busy responding to requests, say dozens or hundreds, and they all require the maximum message size.
Potentially, your server could have to allocate dozens or hundreds of message buffers at the same time – if you have 100 users and each requests 64K, that’s 6.4 MByte – but if you have 200 users and each requests 5 MB – that’s a gigabyte of RAM in the server – just for the message buffers, for one service.
So yes – putting a limit on the max message size does make sense and it helps manage your server’s memory consumption (and thus performance). If you open it up too wide, an attacker might just do such an attack – flooding your server with bogus requests, each allocating as much memory as they can get, ultimately bringing your server down (Denial of Service attacks like that are quite common).