ASP NET TO SQL 2000

[Chris Geier]

Sorry if this is in the wrong group or just a crazy question but..I guess I
am going to ask it anyway.

We have an ASP application connecting to backend SQL 2000 database. We are
in the middle of doing performance and load testing and are finding
intermetant problems with connection time outs. There are no hardware
resource issues. CPU, Memory etc are all under 15% utilization. My theory is
that we have some kind of connection leak and after a period of time the
webserver starts to timeout waiting for connections and throws the
error/excetption back to the client/testing tools (timeout expired prior to
obtaining a connection from the connection pool) this is the error I get on
the testing tool. In my web.config I have connection pool max set at 100.
and in my perf counters i see current connection pools global= 9 current
pooled and non pooled connections= 40. Those are from the webserver. I am
at a loss trying to figure out what is going on between the webserver and SQL
server that is causing the timeout. It would appear that I am not getting
near the pool max. What else should I be looking at, what am I missing, what
to do?

[J.P. Cummins]

Perhaps it is a session variable timing out.

--
J.P. Cummins
jp*******@gmail.com

Chris Geier wrote:

Sorry if this is in the wrong group or just a crazy question but..I guess I
am going to ask it anyway.

We have an ASP application connecting to backend SQL 2000 database. We are
in the middle of doing performance and load testing and are finding
intermetant problems with connection time outs. There are no hardware
resource issues. CPU, Memory etc are all under 15% utilization. My theory is
that we have some kind of connection leak and after a period of time the
webserver starts to timeout waiting for connections and throws the
error/excetption back to the client/testing tools (timeout expired prior to
obtaining a connection from the connection pool) this is the error I get on
the testing tool. In my web.config I have connection pool max set at 100.
and in my perf counters i see current connection pools global= 9 current
pooled and non pooled connections= 40. Those are from the webserver. I am
at a loss trying to figure out what is going on between the webserver and SQL
server that is causing the timeout. It would appear that I am not getting
near the pool max. What else should I be looking at, what am I missing, what
to do?

[bruce barker]

one common reason for this is a slow domain controller if you are using
intergated security. the connection timeout happens trying to authenticate
the sql login. a simple test is to convert to sql standard security for the
test, and see if the problem goes away.

-- bruce (sqlwork.com)

"Chris Geier" <chris.geier at gmail.com> wrote in message
news:9D**********************************@microsof t.com...
| Sorry if this is in the wrong group or just a crazy question but..I guess
I
| am going to ask it anyway.
|
| We have an ASP application connecting to backend SQL 2000 database. We
are
| in the middle of doing performance and load testing and are finding
| intermetant problems with connection time outs. There are no hardware
| resource issues. CPU, Memory etc are all under 15% utilization. My theory
is
| that we have some kind of connection leak and after a period of time the
| webserver starts to timeout waiting for connections and throws the
| error/excetption back to the client/testing tools (timeout expired prior
to
| obtaining a connection from the connection pool) this is the error I get
on
| the testing tool. In my web.config I have connection pool max set at 100.
| and in my perf counters i see current connection pools global= 9 current
| pooled and non pooled connections= 40. Those are from the webserver. I
am
| at a loss trying to figure out what is going on between the webserver and
SQL
| server that is causing the timeout. It would appear that I am not getting
| near the pool max. What else should I be looking at, what am I missing,
what
| to do?
|