Maximum number of items that can be serialized or deserialized in an object graph is '65536'

Ciaran O Neill

18y16.5k

Hi,

I'm trying to debug a problem that's occurring when sending large amounts of data over WCF. The error message from the System.ServiceModel.CommunicationException that's being thrown is:
"There was an error while trying to serialize parameter http://tempuri.org/:batch. The InnerException message was 'Maximum number of items that can be serialized or deserialized in an object graph is '65536'. Change the object graph or increase the MaxItemsInObjectGraph quota. '. Please see InnerException for more details."

I've tried changing everything I could find in both the service web.config and the client app.config, but nothing is working for me. My relevant sections from web.config are:



































The sections from the app.config are:


















                      bindingConfiguration="WSHttpBinding_ISyncEndpoint" contract="SyncWebService.ISyncEndpoint" name="WSHttpBinding_ISyncEndpoint"
                behaviorConfiguration="WSHttpBinding_ISyncEndpoint_Behaviour" />










This is causing me a big problem, so if anyone has an idea it would be much appreciated.

TIA,
Ciaran O'Neill

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Tom Jackson16y ago
I saw it at the link I gave but there was no documentation there on how to set it (parameter of what method?), where it goes (web.config?), etc. Also, I'm not sure I could convince our customer to allow us to change it, anyway, since it relates to helping to prevent denial-of-service attacks. If you have some info on it, though, it might be good to know how to use it (and for future readers of this thread).

Thanks,
Tom

0
Sam Hobbs16y ago
Did you specify a larger value for MaxItemsInObjectGraph? Did you also read the documentation of MaxItemsInObjectGraph?
0
Tom Jackson16y ago
According to http://msdn.microsoft.com/en-us/library/ms731073.aspx, 65536 is the limit on the amount of data (in my case, number of rows from a database I was returning to an object via a web service call, where this exception occurred) that can be sent. Looked up this thread and thought maybe someone found a way around it, but I looked a little deeper - it's in the SOAP conversion that the error is given - way deep in the .NET layers in the serialization of the data across the wire, not anything in the code you can change yourself. I'm thinking this might just be a limitation of SOAP/.NET, but would love for someone to prove I'm wrong so we could do more per call.

-Tom
0