| Aniello 2004-10-18, 7:46 am |
|
Dear all,
I have an orchestration published as web service. Inside it there are two
ports hooked on two web services that call an other orchestration
published as web service. This second orchestration runs for a long time
(about 4 minutes) for this reason I receive an exception in the first
orchestration, because the result doesn't come back in time.
I have increased the IIS timeout (600 seconds), the httpRuntime tag of
machine.config file (600 seconds), on the send ports of web services I
have tried to change the timeout, but I'm able to change only the Retry
Count and Retry Interval content. In these ways I haven't able to solve the
problem.
I can't set an high timeout value using
MyMessage(SOAP.ClientConnectionTimeout) = ...
because my orchestration MUST be BPEL compliant.
Does anyone know how to increase the timeout in order to avoid this error?
Thanks,
Aniello.
|