Get started for free
Visual Studio Developer Center >
> 
> 
Unable to read data from the transport connection

Answered Unable to read data from the transport connection

  • Thursday, December 01, 2011 4:44 PM
     
     
    Sign In to Vote
    0

    Hi there,

    I'm using BizTalk Server 2010, I have a "standard" WCF-BasicHttp sollicit Response Send port.

    For one of my WebService that this port calls (the webservice is written in php5), I got the error :

    System.ServiceModel.CommunicationException: An error (Unable to read data from the transport connection: The connection was closed.) occurred while transmitting data over the HTTP channel. ---> System.IO.IOException: Unable to read data from the transport connection: The connection was closed.

    I tried to use the WCF-Custom with WCF-BaicHttp binding where I had more options, where I increased the maximum receive size, buffer..., but still I got the exact same error.

    Is there any nice work around for this? or is there any work around at all?

    By the way SOAPUI handles this WebSerivce with no issue, and the WebService with soapui responds quickly.

    The problem can be reproduced all the time for the same parameters

    Regards,

    Stefan

    BizTalk Consultant in France
     

All Replies

  • Monday, December 05, 2011 2:47 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hello, I don't know BizTalk. You can also ask the question on http://www.microsoft.com/biztalk/en/us/forums.aspx.

    One potential problem can be ASP.NET's httpRuntim.maxRequestLength is set too low. Refer to http://social.msdn.microsoft.com/Forums/en/wcf/thread/496e72ef-48cf-4f87-9285-fa9d175f5bd7 for more information.

    Lante, shanaolanxing This posting is provided "AS IS" with no warranties, and confers no rights.
    If you have feedback about forum business, please contact msdnmg@microsoft.com. But please do not ask technical questions in the email.
     
  • Monday, December 05, 2011 8:59 AM
     
     Answered
    Sign In to Vote
    0

    I finally found out the problem, but still don't know about a "sexy" solution though, if fact what was causing the problem was the keep alive parameter (fixed to 5 seconds and the WebService responded in some cases in more than 5 seconds which was causing WCF and the .NET framework in general to fail)

    To illustrate this I developped a winform application where I imported a WebReference (old school) and still it failed.

    When I looked closely to the Response of the WebService I noticed this Keep-Alive parameter.

    Is there a way in WCF to by pass this parameter? As usual the SOAPUI functions correctly, why does is it all the times that this SOAP UI works correctly ? hmmmm

    Regards,

    Stefan

     

    BizTalk Consultant in France