none
One-way: HTTP Send port error RRS feed

  • Question

  • We have a one-way HTTP send port and we did this error for some of the messages (not for all)

    The HTTP send adapter cannot complete the transmission within the specified time.

     Destination: http://.....url...

    Some of the blogs refer to this error would occur in Solicit-response ports, but in our case its in a one-way send port.

    Can any one suggest us some solution. Its in production server, so we can use any network sniffer tools.

    Wednesday, December 4, 2013 11:13 AM

Answers

  • HTTP send adapter send the message to a destination URL on an HTTP POST. So for HTTP post to get HTTP-200 status (success status) there will a response (even you have used one-way, this is HTTP handshake) which will contain an entity describing or containing the result of the action. So in your case this response/handshake seems to take longer time to come.

    As la Cour suggested setting to HttpOutTimeoutInterval shall help you and this would affect all the send port adapter instances in that particular host.

    I think still RequestTimeout setting (in send port’s adapter properties) would help in your case. If you had used fiddler or any network sniffer tools, you can see theOverall Elapsed:” time this would give the time taken between Client Connected and Client Response. To calculate the timeoutvalue you can use the formula

    Timeout = Min((180sec + ((MessageSize* 3)/1000)), 3600sec)

    Otherwise to test if this works, start with some longer timeout value in  RequestTimeout setting.


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

    • Marked as answer by AskQues Wednesday, December 4, 2013 4:47 PM
    Wednesday, December 4, 2013 12:15 PM

All replies

  • I would assume that this occurs when you are dealing with large messages or maybe when you send many messages at the same time? You might need to increase the HTTPOutTimeoutInterval or HTTP maxconnection, read more here:

    http://msdn.microsoft.com/en-us/library/aa547969.aspx

    Morten la Cour

    Wednesday, December 4, 2013 11:27 AM
  • HTTP send adapter send the message to a destination URL on an HTTP POST. So for HTTP post to get HTTP-200 status (success status) there will a response (even you have used one-way, this is HTTP handshake) which will contain an entity describing or containing the result of the action. So in your case this response/handshake seems to take longer time to come.

    As la Cour suggested setting to HttpOutTimeoutInterval shall help you and this would affect all the send port adapter instances in that particular host.

    I think still RequestTimeout setting (in send port’s adapter properties) would help in your case. If you had used fiddler or any network sniffer tools, you can see theOverall Elapsed:” time this would give the time taken between Client Connected and Client Response. To calculate the timeoutvalue you can use the formula

    Timeout = Min((180sec + ((MessageSize* 3)/1000)), 3600sec)

    Otherwise to test if this works, start with some longer timeout value in  RequestTimeout setting.


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

    • Marked as answer by AskQues Wednesday, December 4, 2013 4:47 PM
    Wednesday, December 4, 2013 12:15 PM
  • @la Cour: Thanks for info. We have many HTTP send port configured for under a particular host.

    @ Ashwin: So set the Request Timeout setting for 600 sec (10 mins) it worked.

    Thanks you la Cour and Ashwin for your help.

    Wednesday, December 4, 2013 4:49 PM