none
Biztalk WCF-NetTcp adapter, "The response message body was not read" RRS feed

  • Question

  • Hi ,

    I have got an error System.ApplicationException: The response message body was not read.  (This may indicate the connection has been closed.) We use a orchestration and use the xml Receive pipeline and the port type :Request-Response .We use WCF-NetTcp adapter.So when I get the timeout error if I restart the host instance then the error seems to disappear and everything seems fine.

    Monday, January 25, 2016 12:22 AM

Answers

  • I suspect the TCP connection is getting closed/aborted.

    Two things that you can try before the issue is reproduced the next time-

    1)Network trace

    2)WCF trace

    Alternatively, set the WCF Send/Receive TimeOut values to larger values than the default of 10mins to some randomly large value like 10hrs/20hrs and give it a try.

    • Proposed as answer by Angie Xu Tuesday, February 2, 2016 1:36 AM
    • Marked as answer by Angie Xu Tuesday, February 2, 2016 1:37 AM
    Monday, January 25, 2016 8:36 AM
    Moderator

All replies

  • Hi,

    Refer :https://social.msdn.microsoft.com/Forums/en-US/c6094458-ea67-490e-959a-491477d18c21/wcfnettcp-adapter-the-response-message-body-was-not-read?forum=biztalkr2adapters

    This sounds to me like BizTalk is polling the WCF-NetTCP service and occasionally the service is unloaded or down and it does not respond within the timeout interval. Is it possible the NetTCP service goes down occasionally or is unloaded like with IIS recycling?

    One way to get around this without the port crashing (and requiring a host restart) may be to increase the retry number or retry interval (see the Transport Advanced Options tab in the port properties).

    https://msdn.microsoft.com/en-us/library/bb743422.aspx

    Thanks

    Abhishek


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Monday, January 25, 2016 1:35 AM
  • I suspect the TCP connection is getting closed/aborted.

    Two things that you can try before the issue is reproduced the next time-

    1)Network trace

    2)WCF trace

    Alternatively, set the WCF Send/Receive TimeOut values to larger values than the default of 10mins to some randomly large value like 10hrs/20hrs and give it a try.

    • Proposed as answer by Angie Xu Tuesday, February 2, 2016 1:36 AM
    • Marked as answer by Angie Xu Tuesday, February 2, 2016 1:37 AM
    Monday, January 25, 2016 8:36 AM
    Moderator
  • Also, the connection maybe getting reset at the client/calling application side - check what are the Send Timeout and Receive Timeout values there and increase appropriately as well.
    Monday, January 25, 2016 8:41 AM
    Moderator
  • Hi Sranjani.

    Thank you for posting on MSDN forum.

    Have you seen any error logged in event viewer, Please have a look into event viewer and verify anything logged there.


    Thanks,

    If my reply is helpful please mark as Answer or vote as Helpful.

    My blog | Twitter | LinkedIn

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Monday, January 25, 2016 9:12 AM