none
Response Status to Code to Client when send port get timed out RRS feed

  • Question

  • What HTTP status code is received by the client when send port get timed out and suspend in the admin console?

    1. The client is consumed BizTalk service which hosted in the IIS and configured in the BizTalk receive location  
    2. It’s messaging solution, Send port subscribes the message and send to rest service through a web - http adapter
    3. If the sending port got timed out and suspend in the admin console, What status code returns to the client?


    Friday, September 13, 2019 8:19 PM

All replies

  • well if Send port is getting timeout, I believe as you should be sending using REST API connecting to external (system).So, if for some reason if entity doesnt match or issue on their side it throws as 500 Server error.

    Or, if there is anything like on your side if the token doesnt match, then you get 404 error


    RH

    Friday, September 13, 2019 9:35 PM
  • I have tried to prove and followed below steps.

    1. Create schema as a service , publish into IIS and configured receive location
    2. Created WCF service and kept delay for long time and hosted
    3. Created send port and configured send port filter
    4. Tested through soapui which returns time out and doesn’t return any http code
    Friday, September 13, 2019 10:27 PM
  • check your website is pointed to correct AppPool which has access to the Host instance.

    RH

    Sunday, September 15, 2019 5:34 PM
  • It the client is timing out, by definition you won't be getting a response, hence no response code.

    If you want to ensure that there is a response, then you need to ensure that either something in BizTalk or the end point that BizTalk consumes sends a response before the client can time out.  In which case I would want to send a 408 http status code.

    408 Request Timeout

    The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."

    The easiest way to send a response like that in BizTalk would usually be in an Orchestration.


    Monday, September 16, 2019 2:44 AM