you've coded such that no pooling is effectively used, as you are using
the same connection for all requests. also as you do not lock the
connection during use (by sqlcommands), two page requests that try to
use the connection at the same time will fail.
you should only keep the connection string in application, and create a
connection for each request. this will enable pooling to be be used by
every request.
-- bruce (sqlwork.com)
> I try to do the following:
>
[quoted text clipped - 49 lines]
>
> Thomas
Tom - 13 Sep 2007 06:34 GMT
Thanks for that input bruce. So does this mean, that ASP is managing the
pool in the background transparently? In J2EE you have to configure
connection pools in the container (application server) for every
application.
I hope ASP connection pools are also on application context and not on
page context!
Tom
bruce barker schrieb:
> you've coded such that no pooling is effectively used, as you are using
> the same connection for all requests. also as you do not lock the
[quoted text clipped - 6 lines]
>
> -- bruce (sqlwork.com)