WCF-Custom

Viewing 1 reply thread
  • Author
    Posts
    • #20649

       I think I found a reson for the necessity of the WCF-Custom adapter.
      We are processing large amounts of complex data, and we were getting the error “Connection closed unexpectedly”.
      By doing a service side trace, we learned that the real 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. ‘. 

       

       

       

       

       

       

      In C# client, the solution was to add this XML to the app.config (and similar to web.config).
      <

      behaviors>
        <
      endpointBehaviors>
            <
      behavior name=LargeEndpointBehavior>
                <
      dataContractSerializer maxItemsInObjectGraph=10000000 />
            </
      behavior>
        </
      endpointBehaviors>
      </
      behaviors>

      I used the import function to get this into a custom pipeline, but then still got the same message.
      Has anybody been down this road before?

      Thanks,
      Neal Walters


    • #20651

      From your post, it sounds like BizTalk is acting as a client in this scenario.  Did you apply the behavior on the service side as well?

      • #20654

         You need to  set the maxReceivedMessageSize attribute on the http transport bindings. This can be done using the receive location config UI.

        • #20717

           I set the maxReceivedMessageSize a long time ago.  This is a totally new error related to the size of the “object graph”.

          I did create a custom port.  There was a button on the last tab to import an app.config, which I did, and it set up the parm on the custom config tab.  However, it still didn’t work – I need to test more as soon as I deal with higher priority issues.

          Neal

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.