IIS connection pool timeouts with XML response content type

Help!

I get connection pool timeouts when I perform a GET with querystring params
that return a contenttype = "text/xml" doc.

I have multiple clients that request the same URL and the XML doc returns
updated data every 1 second.

Example: Similar to multiple clients that retrieve stock quotes every 1
second.

I swear this did not happen when I was running under .NET V1. Could have
been a service patch though.

My .NET server app simply queries the SQL Server 200 DB with Microsoft data
application blocks, builds an XML doc string, and response.writes it to the
client.

The client is using asynch calls from a VB6 app using the MSXML2.XMLHTTP.
It performs a simple get http://foo.com/p.aspx?A=11
When state = 4 I parse the return data and call the url again.

I am running version .NET v1.1.4322
I tested this on 3 machines with the same result
Win2K
Win3K
WinXP

You can also trigger the timeout by placing the url in a browser and click
the refresh button many times.

Perf mon show web connections stay around 2 until something trips up and the
connection count soars and the browser GET command fails with a Max
connection pool error.

It takes the server about 5 minutes to recover.

What gives!

Thanks

Tom

Tom
Thu Jul 10 19:20:27 CDT 2003

Thie problem was connection pooling for my SQL Server data connection see
http://asia.cnet.com/itmanager/tech/0,39006407,39117800-2,00.htm for a
complete description of the problem.

Adjusting Max Pool Size for my connection string fixed it.


"Tom Thomas" <me@nospamplease.com> wrote in message
news:O2gUizyRDHA.3796@tk2msftngp13.phx.gbl...
> Help!
>
> I get connection pool timeouts when I perform a GET with querystring
params
> that return a contenttype = "text/xml" doc.
>
> I have multiple clients that request the same URL and the XML doc returns
> updated data every 1 second.
>
> Example: Similar to multiple clients that retrieve stock quotes every 1
> second.
>
> I swear this did not happen when I was running under .NET V1. Could have
> been a service patch though.
>
> My .NET server app simply queries the SQL Server 200 DB with Microsoft
data
> application blocks, builds an XML doc string, and response.writes it to
the
> client.
>
> The client is using asynch calls from a VB6 app using the MSXML2.XMLHTTP.
> It performs a simple get http://foo.com/p.aspx?A=11
> When state = 4 I parse the return data and call the url again.
>
> I am running version .NET v1.1.4322
> I tested this on 3 machines with the same result
> Win2K
> Win3K
> WinXP
>
> You can also trigger the timeout by placing the url in a browser and click
> the refresh button many times.
>
> Perf mon show web connections stay around 2 until something trips up and
the
> connection count soars and the browser GET command fails with a Max
> connection pool error.
>
> It takes the server about 5 minutes to recover.
>
> What gives!
>
> Thanks
>
> Tom
>
>