BizTalk Server Applications Integration - huge number of Timeouts during a call to webservice

Author

huge number of Timeouts during a call to webservice

krishna Pothini

2005-02-23, 5:58 pm

We were getting a huge number of Time outs when BizTalk is calling one
of our internal webservice.
"
The operation has timed-out.
The operation has timed-out.
The underlying connection was closed: The request was canceled.
The underlying connection was closed: The request was canceled.
The request failed with HTTP status 503: Service Unavailable.
The request failed with HTTP status 503: Service Unavailable.
There were not enough free threads in the ThreadPool object to complete
the operation.
There were not enough free threads in the ThreadPool object to complete
the operation.
"
These are various kinds of error we are getting.
We don't see BizTalk calling the webservice at all for all this error
messages.After some googling we found that changing the low watermark
and high watermark in the BIztalk using "SvcClassSettings.exe" tool we
could avoid this problem.

Is this problem with the BizTalk soap adapter.I am looking for a better
solution rather than changing the low and high watermark because the
default values are 100&200 we have to make it 6&12 to avoid this
problem,in a way we are limiting the capabilty of BizTalk so much.

Thanks in advance....
Krishna Mohan Pothini.

Stephen Walls [MSFT]

2005-02-25, 7:48 am

Are you hosting your Orchestrations and SOAP adapter on the same server? If
so, you could also try hosting the SOAP adapter on a seperate server, so
that you will have a seperate ThreadPool for use.

--
Stephen Walls [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
"Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"

"krishna Pothini" <pothini@gmail.com> wrote in message
news:1109175726.826029.265860@o13g2000cwo.googlegroups.com...
> We were getting a huge number of Time outs when BizTalk is calling one
> of our internal webservice.
> "
> The operation has timed-out.
> The operation has timed-out.
> The underlying connection was closed: The request was canceled.
> The underlying connection was closed: The request was canceled.
> The request failed with HTTP status 503: Service Unavailable.
> The request failed with HTTP status 503: Service Unavailable.
> There were not enough free threads in the ThreadPool object to complete
> the operation.
> There were not enough free threads in the ThreadPool object to complete
> the operation.
> "
> These are various kinds of error we are getting.
> We don't see BizTalk calling the webservice at all for all this error
> messages.After some googling we found that changing the low watermark
> and high watermark in the BIztalk using "SvcClassSettings.exe" tool we
> could avoid this problem.
>
> Is this problem with the BizTalk soap adapter.I am looking for a better
> solution rather than changing the low and high watermark because the
> default values are 100&200 we have to make it 6&12 to avoid this
> problem,in a way we are limiting the capabilty of BizTalk so much.
>
> Thanks in advance....
> Krishna Mohan Pothini.
>

Nick Doyle

2005-02-25, 7:48 am

I have had the same and the only solution I could think of was
adjusting watermarks as you said.
For a while I thought about writing my own threadpool class, then
modify baseadapter to make use of it, but it was work (heh). Still,
there are examples of the first bit out there.
So you got a threadpool with 24 (i think) threads, each having to wait
a half-second for the call to complete. When you hammer him you're
going to run out of threads pretty quick, you need to tell biztalk to
ease up by adjusting these settings.
I'm sure there are people much more educated on this than me and I'd
like to hear their thoughts, because it would be nice to be able to
really pump the messages through.