|
Home > Archive > BizTalk Server General > July 2005 > Biz Talk Web Service Time Out
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 |
Biz Talk Web Service Time Out
|
|
|
| Hi there,
I have a biztalk orchestration that consumes a web service. When I send a
small message to the Web Service which requires a small amount of processing
everything is OK.
However, when I send a larger message which requires the web service to do
more processing I get the following time-out error message reported by
BizTalk:-
The adapter failed to transmit message going to send port "<My Web
Service>". It will be retransmitted after the retry interval specified for
this Send Port. Details:"The operation has timed-out.".
I know that the web service is happily processing away, yet it seems Biztalk
refuses to wait for it to finish.
I've modified the Web.config file of teh Web Service to increase to time-out
with the following elements: -
<httpRuntime maxRequestLength="1000000" useFullyQualifiedRedirectUrl="true"
executionTimeout="3600" />
Is there something that I need to set in Biztalk in order for it to wait for
my webservice to return???
Thanks,
Dave.
| |
|
| I might also add that after finding a similar thread, I added the following
expressions to my orchestration.....
MyMessage(SOAP.ClientConnectionTimeout) = 180000;
MyMessage(HTTP.RequestTimeout) = 180000;
I'm still getting the same problem.
Thanks,
Dave.
"Dave" wrote:
> Hi there,
>
> I have a biztalk orchestration that consumes a web service. When I send a
> small message to the Web Service which requires a small amount of processing
> everything is OK.
>
> However, when I send a larger message which requires the web service to do
> more processing I get the following time-out error message reported by
> BizTalk:-
>
> The adapter failed to transmit message going to send port "<My Web
> Service>". It will be retransmitted after the retry interval specified for
> this Send Port. Details:"The operation has timed-out.".
>
> I know that the web service is happily processing away, yet it seems Biztalk
> refuses to wait for it to finish.
>
> I've modified the Web.config file of teh Web Service to increase to time-out
> with the following elements: -
>
> <httpRuntime maxRequestLength="1000000" useFullyQualifiedRedirectUrl="true"
> executionTimeout="3600" />
>
> Is there something that I need to set in Biztalk in order for it to wait for
> my webservice to return???
>
> Thanks,
> Dave.
| |
| Tomas Restrepo \(MVP\) 2005-07-11, 2:48 am |
| Dave,
> I have a biztalk orchestration that consumes a web service. When I send a
> small message to the Web Service which requires a small amount of
> processing
> everything is OK.
>
> However, when I send a larger message which requires the web service to do
> more processing I get the following time-out error message reported by
> BizTalk:-
>
> Is there something that I need to set in Biztalk in order for it to wait
> for
> my webservice to return???
I believe you need to tell the SOAP adapter to wait a longer time for the
server's response, by setting the SOAP.ClientConnectionTimeout property on
the request message sent to the service (you can do this when you construct
the service's request message in a message assignment shape).
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| BizTalk Benjamin 2005-07-12, 5:55 pm |
| Tomas/Dave,
We have the same problem and I am setting the ClientConnectionTimeout on the
message that goes to the Web Service but it still times out. I tried various
values of the timeout like 10000 or even -1 (which is often used in a
ordinary client proxy to make sure there is no timeout. Of course in BTS you
cant set stuff on the proxy directly)
The only workaround we can think of is to debatch the message into very
small sizes. This does result in a very chatty interface to the web service,
but if we cant solve the timeout then there isnt anything else we can do.
Suggestions anyone?
Benjy
"Tomas Restrepo (MVP)" wrote:
> Dave,
>
>
> I believe you need to tell the SOAP adapter to wait a longer time for the
> server's response, by setting the SOAP.ClientConnectionTimeout property on
> the request message sent to the service (you can do this when you construct
> the service's request message in a message assignment shape).
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Tomas Restrepo \(MVP\) 2005-07-13, 8:52 pm |
| Benjamin,
> Tomas/Dave,
> We have the same problem and I am setting the ClientConnectionTimeout on
> the
> message that goes to the Web Service but it still times out. I tried
> various
> values of the timeout like 10000 or even -1 (which is often used in a
> ordinary client proxy to make sure there is no timeout. Of course in BTS
> you
> cant set stuff on the proxy directly)
Here's some more info:
I've checked, and the value of the ClientConnectionTimeout property is
specified in Milliseconds, as it maps directly to the Timeout property of
the SoapHttpClientProtocol class. However, it has to be > 0, because the
SOAP Adapter code actually checks explicitly does a check and only takes the
value into account if it is larger than 0 (the whole "0 means it uses a
value depending on the message size" seems to be baloony).
That said, I've been doing some tests here with it, and it seems to work
pretty fine... I've gotten it to wait 200 seconds that way with no problems
whatsoever. One thing that you might want to look as well is check that your
service itself is not timing out (since ASP.NET will also time out requests
whose execution takes more than a certain ammount of time).
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| BizTalk Benjamin 2005-07-14, 7:47 am |
| Hi Tomas,
Thanks. Its useful to know that -1 does not work in the SOAP Adapter. Heres
my situation.
I have this web service that takes an XmlDocument and de-serialises it into
a set of business classes that get persisted into a database (via the EntLib
DAAB and SP's).
We unit tested it with NUnit and used a message size 50000 records with a
commit batch size of 1000. There is no timeout so its not an ASP.NET timeout
issue.
However, when we call the web service from BizTalk , thats when the Event
Log shows the time-out in a series of messages shown below
MESSAGES
-------------
8.The configuration information of the performance library
"C:\WINNT\system32\inetsrv\w3ctrs.dll" for the "W3SVC" service does not match
the trusted performance library information stored in the registry. The
functions in this library will not be treated as trusted.
9.Microsoft FrontPage Server Extensions:
(OS Error #-1073741819 Message: exception occurred at 0x67ee8439)
10.Microsoft FrontPage Server Extensions:
file:// - Error #80002 Message: System exception: access violation.
11.The Messaging Engine has suspended "1" message(s) from adapter "SOAP" due
to failures in message processing. Please refer to Health and Activity
Tracking tool for more detailed information on this failure.
12.The "SOAP" adapter is suspending an outbound message going to destination
URL:"http://localhost/DataExchange/Dataloadservice/SupplierData.asmx".
Details:"The operation has timed-out.".
13.The adapter "SOAP" raised an error message. Details "The operation has
timed-out.".
-----------------
Have you come across these? the first couple of messages seem very strange
indeed.
Benjy
"Tomas Restrepo (MVP)" wrote:
> Benjamin,
>
>
> Here's some more info:
>
> I've checked, and the value of the ClientConnectionTimeout property is
> specified in Milliseconds, as it maps directly to the Timeout property of
> the SoapHttpClientProtocol class. However, it has to be > 0, because the
> SOAP Adapter code actually checks explicitly does a check and only takes the
> value into account if it is larger than 0 (the whole "0 means it uses a
> value depending on the message size" seems to be baloony).
>
> That said, I've been doing some tests here with it, and it seems to work
> pretty fine... I've gotten it to wait 200 seconds that way with no problems
> whatsoever. One thing that you might want to look as well is check that your
> service itself is not timing out (since ASP.NET will also time out requests
> whose execution takes more than a certain ammount of time).
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>
| |
| Tomas Restrepo \(MVP\) 2005-07-14, 7:47 am |
| Benjamin,
> Thanks. Its useful to know that -1 does not work in the SOAP Adapter.
> Heres
> my situation.
>
> I have this web service that takes an XmlDocument and de-serialises it
> into
> a set of business classes that get persisted into a database (via the
> EntLib
> DAAB and SP's).
> We unit tested it with NUnit and used a message size 50000 records with a
> commit batch size of 1000. There is no timeout so its not an ASP.NET
> timeout
> issue.
>
> However, when we call the web service from BizTalk , thats when the Event
> Log shows the time-out in a series of messages shown below
>
> MESSAGES
> -------------
> 8.The configuration information of the performance library
> "C:\WINNT\system32\inetsrv\w3ctrs.dll" for the "W3SVC" service does not
> match
> the trusted performance library information stored in the registry. The
> functions in this library will not be treated as trusted.
>
> 9.Microsoft FrontPage Server Extensions:
> (OS Error #-1073741819 Message: exception occurred at 0x67ee8439)
>
> 10.Microsoft FrontPage Server Extensions:
> file:// - Error #80002 Message: System exception: access violation.
>
> 11.The Messaging Engine has suspended "1" message(s) from adapter "SOAP"
> due
> to failures in message processing. Please refer to Health and Activity
> Tracking tool for more detailed information on this failure.
>
> 12.The "SOAP" adapter is suspending an outbound message going to
> destination
> URL:"http://localhost/DataExchange/Dataloadservice/SupplierData.asmx".
> Details:"The operation has timed-out.".
>
> 13.The adapter "SOAP" raised an error message. Details "The operation has
> timed-out.".
>
> -----------------
> Have you come across these? the first couple of messages seem very strange
> indeed.
Well, it seems like you might have an IIS configuration problem that might
be "triggered" by the biztalk calls (though no idea why). Regarding the
first entries, it sounds like a problem in your configuration of the
Frontpage Server extensions (something similar to this, perhaps?
http://support.microsoft.com/defaul...kb;en-us;832881).... maybe
resolving that clears things up...
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
|
|
|
|
|