|
Home > Archive > BizTalk Server Orchestration > November 2005 > Timeout when calling webservice from orchestration
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Timeout when calling webservice from orchestration
|
|
| Kekilie 2005-11-16, 7:52 am |
| Hi,
I get timeout from a wbeservice even though I have set
SOAP.ClientConnectionTimeout=12000 and HTTP.RequestTimeout=12000.
Why?
Situation:
I an orchestration that calls webservice methods, 3 different
methods. All of them receive one xml as a parameter. The xml's are populated
from database tables, three different tables. 2 of the webservice calls works
fine, 1 results in a timeout. The xml's in the 2 calls that succeeds contains
data from database tables with 500 and 900 rows. These 2 calls returns back
to the orchestration with a response. The call that fails contains a xml with
data from 13500 database table rows! I thought that maybe the webservice
needed more time, so I added the following code in the Assignment shape just
before the webservice call in my orchestration :
Msg_SOAPRequest(SOAP.ClientConnectionTimeout) = 12000;
Msg_SOAPRequest(HTTP.RequestTimeout) = 12000;
This code had no effect! Still get timeout, and I get it immediately after
the request is sent. It doesnt wait for 3 minutes before it times out (if
12000 milliseconds is like 3 minutes...)
Any ideas to fix this timeout?
Or to troubleshoot? Is there anything else than my orchestration that can
cause this error? In that case what?
Regards,
Kekilie
| |
| Fredrik M 2005-11-16, 5:57 pm |
| Make sure you have also set the connection timeout on the web server you are
consuming.
| |
| Kekilie 2005-11-28, 6:02 pm |
| Do you mean the webserver running the webservice I'm calling from my BizTalk
orchestration? The webservice is running on a remote webserver on the
Internet. Out of my reach. Can ask the ones responsible for this webservice
to do it.
Is there anything else I can do on my side to fix this timeout problem other
than setting SOAP.ClientConnectionTimeout and HTTP.RequestTimeout? Is there a
max value to use on SOAP.ClientConnectionTimeout and HTTP.RequestTimeout?
Regards,
Kekilie
"Fredrik M" wrote:
> Make sure you have also set the connection timeout on the web server you are
> consuming.
>
|
|
|
|
|