WCF Adapter Send Timeout calculates behaviour and custom pipeline components code execution time RRS feed

  • Question

  • As per error the send port got timed out from external service but the service returned response in  a 15 seconds.

    Does send port send timeout  calculates custom pipeline components and WCF behaviors execution time?

    Example :

    Send TimeOut:00:01:00

    Pipeline components execution time:50 seconds

    Behavior : 25 seconds

    External service :25 seconds

    The send port couldn’t able to returned the response in a minute because send timeout which calculates the time which response need to receive from the external service

    <SOAP:Envelope xmlns:SOAP="" SOAP:encodingStyle=""><SOAP:Body><SOAP:Fault><faultcode>Microsoft BizTalk Server Negative Acknowledgment </faultcode><faultstring>An error occurred while processing the message, refer to the details section for more information </faultstring><faultactor>'</faultactor><detail><ns0:NACK Type="NACK" xmlns:ns0=""><NAckID>{59310FE1-FC15-42EE-A552-CCD0B6E15598}</NAckID><ErrorCode>0xc0c0167a</ErrorCode><ErrorCategory>0</ErrorCategory><ErrorDescription>System.TimeoutException: The HTTP request to ''

    Could you please clear up my doubt.

    Thank you in advanced

    Monday, November 25, 2019 4:49 PM

All replies

  • I believe the time is measured from the moment the message is committed to the message box.   So if you have a send port that is very busy and maybe throttling, then you can get messages timing out in BizTalk.   I think the reason for this behavior is that your send port may be getting it's messages from a Request-Response receive location that would time-out otherwise.
    Tuesday, November 26, 2019 8:06 PM