Configuring the timeout for a Send Port

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Configuring the timeout for a Send Port

Viewing 1 reply thread
  • Author
    Posts
    • May 9, 2006 at 1:28 PM #14640
      community-content

        I have an orchestration that makes a call to a web service. The web service starts the SQL Server DTExec utility, which runs a SQL Server Integration Services (SSIS) package.

        The orchestration is supposed to wait for a response from the web service. If the web service does not send a response within 5 minutes, I receive this error message:

        [i:d6bda01fdc]
        Event Type: Warning
        Event Source: BizTalk Server 2006
        Event Category: BizTalk Server 2006
        Event ID: 5743
        Date: 05/08/2006
        Time: 11:07:08
        User: N/A
        Computer: BIZTALKDEV2
        Description:
        The adapter failed to transmit message going to send port \”DINEWebService\” with URL \”http://ykclnsd/DINEWebService/Service.asmx\”. It will be retransmitted after the retry interval specified for this Send Port. Details:\”WebException: The operation has timed out \”.[/i:d6bda01fdc]

        The SSIS package will run several data loads that will take hours to complete. I must find a way to increase the timeout for this Send Port, but I don’t see any SendPort properties that allow me to configure the timeout. The only property that even comes close is:

        Transport Advanced Options -> Transport Options -> Retry Interval

        Is the timeout a property that can be set in the Administration console, or do we need to do custom coding? Is there something else I should be looking at in order to resolve this problem?

        Thanks in advance for your assistance.

        • May 15, 2006 at 10:03 AM #14641
          community-content

            You can use SOAP.ClientConnectionTimeout

            Put the following in a message assignment:
            [code:1:04ffa04300]The_Message_Youre_Sending(SOAP.ClientConnectionTimeout) = 1800000;[/code:1:04ffa04300]

            And you will have a 30minute (1800000 milliseconds) timeout instead. But for operations that can take several hours you’re probably better off using greg’s methods.

        • May 9, 2006 at 7:18 PM #14639
          community-content

            I don’t think you can extend the time out to hours.

            An ansynchronous pattern would be far more suitable.
            You call the web service which starts the DTS package and responds immediately. When the DTS package completes it calls back to the orchestration.

        • Author
          Posts
        Viewing 1 reply thread
        • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.