Hi All,

I am running IIS 5.0 on my W2K machine as localhost.  I have a very simple 
ASP page that retrieves data from an MS Access database and displays it on 
the form.  

If I refresh this page several times, I run out of Active Connections on 
the server and I get an error page.  I have made sure to use proper coding 
style by closing and setting to "nothing" both the recordset and 
connection.  In order to monitor Active Connections, I have Personal Web 
Manager open and I see that the Active Connections keep going up and up 
until it hits 10.  Why does it do this? I have configured my ODBC source 
to enable connection pooling.

Any help would be much appreciated...

Jae. 

Are you closing and destroying the connection object at the end of your asp
page?  Every time you refresh the page, if you don't close and destroy the
connection object, it won't go away.  Instead it will remain and a new one
will be added every time you refresh because with each refresh your entire
server side script is re-run.

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:09 PM
To: Access ASP
Subject: [access_asp] Active Connections and Pooling


Hi All,

I am running IIS 5.0 on my W2K machine as localhost.  I have a very simple 
ASP page that retrieves data from an MS Access database and displays it on 
the form.  

If I refresh this page several times, I run out of Active Connections on 
the server and I get an error page.  I have made sure to use proper coding 
style by closing and setting to "nothing" both the recordset and 
connection.  In order to monitor Active Connections, I have Personal Web 
Manager open and I see that the Active Connections keep going up and up 
until it hits 10.  Why does it do this? I have configured my ODBC source 
to enable connection pooling.

Any help would be much appreciated...

Jae. 

Yep I am.  I .Close and also set = nothing all objects that I create.


> Are you closing and destroying the connection object at the end of your 
asp
page?  Every time you refresh the page, if you don't close and destroy the
connection object, it won't go away.  Instead it will remain and a new one
will be added every time you refresh because with each refresh your entire
server side script is re-run.

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:09 PM
To: Access ASP
Subject: [access_asp] Active Connections and Pooling


Hi All,

I am running IIS 5.0 on my W2K machine as localhost.  I have a very simple 
ASP page that retrieves data from an MS Access database and displays it on 
the form.  

If I refresh this page several times, I run out of Active Connections on 
the server and I get an error page.  I have made sure to use proper coding 
style by closing and setting to "nothing" both the recordset and 
connection.  In order to monitor Active Connections, I have Personal Web 
Manager open and I see that the Active Connections keep going up and up 
until it hits 10.  Why does it do this? I have configured my ODBC source 
to enable connection pooling.

Any help would be much appreciated...

Jae. 

Can you send me the error message that you are seeing when it errors out?

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:19 PM
To: Access ASP
Subject: [access_asp] RE: Active Connections and Pooling


Yep I am.  I .Close and also set = nothing all objects that I create.


> Are you closing and destroying the connection object at the end of your 
asp
page?  Every time you refresh the page, if you don't close and destroy the
connection object, it won't go away.  Instead it will remain and a new one
will be added every time you refresh because with each refresh your entire
server side script is re-run.

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:09 PM
To: Access ASP
Subject: [access_asp] Active Connections and Pooling


Hi All,

I am running IIS 5.0 on my W2K machine as localhost.  I have a very simple 
ASP page that retrieves data from an MS Access database and displays it on 
the form.  

If I refresh this page several times, I run out of Active Connections on 
the server and I get an error page.  I have made sure to use proper coding 
style by closing and setting to "nothing" both the recordset and 
connection.  In order to monitor Active Connections, I have Personal Web 
Manager open and I see that the Active Connections keep going up and up 
until it hits 10.  Why does it do this? I have configured my ODBC source 
to enable connection pooling.

Any help would be much appreciated...

Jae. 

Well, what do you know? I restarted my IIS and it seems to be fine now. 
Weird.  The only thing is that I enabled Connection Pooling previously and 
did not restart IIS.  I guess that's all it needed.

Anyway, the error I was getting was a "Too Many Users" error or something 
like that.  It's the documented error you get when you exceed the 
allowable connections.

I appreciate you helping out anyway !!!!!!!! :)


> Can you send me the error message that you are seeing when it errors out?

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:19 PM
To: Access ASP
Subject: [access_asp] RE: Active Connections and Pooling


Yep I am.  I .Close and also set = nothing all objects that I create.


> Are you closing and destroying the connection object at the end of your 
asp
page?  Every time you refresh the page, if you don't close and destroy the
connection object, it won't go away.  Instead it will remain and a new one
will be added every time you refresh because with each refresh your entire
server side script is re-run.

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:09 PM
To: Access ASP
Subject: [access_asp] Active Connections and Pooling


Hi All,

I am running IIS 5.0 on my W2K machine as localhost.  I have a very simple 
ASP page that retrieves data from an MS Access database and displays it on 
the form.  

If I refresh this page several times, I run out of Active Connections on 
the server and I get an error page.  I have made sure to use proper coding 
style by closing and setting to "nothing" both the recordset and 
connection.  In order to monitor Active Connections, I have Personal Web 
Manager open and I see that the Active Connections keep going up and up 
until it hits 10.  Why does it do this? I have configured my ODBC source 
to enable connection pooling.

Any help would be much appreciated...

Jae. 

Yes, you know, in working with IIS over the years, restarting it seems to
resolve a lot of weirdness for me like that.
I understand.

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:52 PM
To: Access ASP
Subject: [access_asp] RE: Active Connections and Pooling


Well, what do you know? I restarted my IIS and it seems to be fine now. 
Weird.  The only thing is that I enabled Connection Pooling previously and 
did not restart IIS.  I guess that's all it needed.

Anyway, the error I was getting was a "Too Many Users" error or something 
like that.  It's the documented error you get when you exceed the 
allowable connections.

I appreciate you helping out anyway !!!!!!!! :)


> Can you send me the error message that you are seeing when it errors out?

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:19 PM
To: Access ASP
Subject: [access_asp] RE: Active Connections and Pooling


Yep I am.  I .Close and also set = nothing all objects that I create.


> Are you closing and destroying the connection object at the end of your 
asp
page?  Every time you refresh the page, if you don't close and destroy the
connection object, it won't go away.  Instead it will remain and a new one
will be added every time you refresh because with each refresh your entire
server side script is re-run.

Karri

-----Original Message-----
From: Jae Hou [mailto:jae@s...]
Sent: Friday, February 21, 2003 3:09 PM
To: Access ASP
Subject: [access_asp] Active Connections and Pooling


Hi All,

I am running IIS 5.0 on my W2K machine as localhost.  I have a very simple 
ASP page that retrieves data from an MS Access database and displays it on 
the form.  

If I refresh this page several times, I run out of Active Connections on 
the server and I get an error page.  I have made sure to use proper coding 
style by closing and setting to "nothing" both the recordset and 
connection.  In order to monitor Active Connections, I have Personal Web 
Manager open and I see that the Active Connections keep going up and up 
until it hits 10.  Why does it do this? I have configured my ODBC source 
to enable connection pooling.

Any help would be much appreciated...

Jae. 

That "too many users" error has nothing to do with ADO/Access/Connection
Pooling. It means you have too many concurrent connections to your *web
server*. PWS (and IIS on Win2k Pro and WinXP Pro) has a hard coded limit of
10 concurrent connections. If you want more connections you need to use
Windows 2000 Server (or Windows NT Server)

Because your browser is probably using "HTTP Keep-Alives" the TCP connection
is kept open to the webserver (this makes performance better because the TCP
connection does not need to created again just to download another image,
but it means you can run out of HTTP connections quicker).

That is why the error goes away when you restart PWS (because all the
connections to the browsers are closed).

Cheers
Ken

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "Jae Hou" <jae@s...>
Subject: [access_asp] RE: Active Connections and Pooling


: Well, what do you know? I restarted my IIS and it seems to be fine now.
: Weird.  The only thing is that I enabled Connection Pooling previously and
: did not restart IIS.  I guess that's all it needed.
:
: Anyway, the error I was getting was a "Too Many Users" error or something
: like that.  It's the documented error you get when you exceed the
: allowable connections.
:
: I appreciate you helping out anyway !!!!!!!! :)
:
:
: > Can you send me the error message that you are seeing when it errors
out?
:
: Karri
:
: -----Original Message-----
: From: Jae Hou [mailto:jae@s...]
: Sent: Friday, February 21, 2003 3:19 PM
: To: Access ASP
: Subject: [access_asp] RE: Active Connections and Pooling
:
:
: Yep I am.  I .Close and also set = nothing all objects that I create.
:
:
: > Are you closing and destroying the connection object at the end of your
: asp
: page?  Every time you refresh the page, if you don't close and destroy the
: connection object, it won't go away.  Instead it will remain and a new one
: will be added every time you refresh because with each refresh your entire
: server side script is re-run.
:
: Karri
:
: -----Original Message-----
: From: Jae Hou [mailto:jae@s...]
: Sent: Friday, February 21, 2003 3:09 PM
: To: Access ASP
: Subject: [access_asp] Active Connections and Pooling
:
:
: Hi All,
:
: I am running IIS 5.0 on my W2K machine as localhost.  I have a very simple
: ASP page that retrieves data from an MS Access database and displays it on
: the form.
:
: If I refresh this page several times, I run out of Active Connections on
: the server and I get an error page.  I have made sure to use proper coding
: style by closing and setting to "nothing" both the recordset and
: connection.  In order to monitor Active Connections, I have Personal Web
: Manager open and I see that the Active Connections keep going up and up
: until it hits 10.  Why does it do this? I have configured my ODBC source
: to enable connection pooling.
:
: Any help would be much appreciated...