 | |
Database server connection limit exceeded
sybase.public.sqlanywhere.general sybase.public.sqlanywhere.general
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Database server connection limit exceeded -
01-22-2010
, 10:52 AM
#2
| |||
| |||
|
|
We are using Adaptive Server Anywhere 9 for a website coded in ASP.Net (2003). We use services for each database. Each service is set as a "Personal Database Server" (there was a reason for this when we first set them up which escapes me now). We get an error when doing a long, iterative, process stating "Database server connection limit exceeded". The ASP.Net code closes the connection each iteration, but this error is still incurred. I notice on the website that a "Personal" database has a limit of 10, whereas a "Network" database has as per licence. I also noticed that the Microsoft Connection Pool could be an issue. Could you clarify what should be done to ensure this error does not occur? |
#3
| |||
| |||
|
|
We are using Adaptive Server Anywhere 9 for a website coded in ASP.Net (2003). We use services for each database. Each service is set as a "Personal Database Server" (there was a reason for this when we first set them up which escapes me now). We get an error when doing a long, iterative, process stating "Database server connection limit exceeded". The ASP.Net code closes the connection each iteration, but this error is still incurred. I notice on the website that a "Personal" database has a limit of 10, whereas a "Network" database has as per licence. I also noticed that the Microsoft Connection Pool could be an issue. Could you clarify what should be done to ensure this error does not occur? |
#4
| |||
| |||
|
|
NOTE: The personal server is not licensed for such use. The personal server is licensed for use in a standalone, single-user application. ASP.Net is not designed to be standalone and generally not a single user. -chris S. Male wrote: We are using Adaptive Server Anywhere 9 for a website coded in ASP.Net (2003). We use services for each database. Each service is set as a "Personal Database Server" (there was a reason for this when we first set them up which escapes me now). We get an error when doing a long, iterative, process stating "Database server connection limit exceeded". The ASP.Net code closes the connection each iteration, but this error is still incurred. I notice on the website that a "Personal" database has a limit of 10, whereas a "Network" database has as per licence. I also noticed that the Microsoft Connection Pool could be an issue. Could you clarify what should be done to ensure this error does not occur? |
#5
| |||
| |||
|
|
When using connection pooling, closing the connection will not actually close it, it is instead returned to the pool to be reused. This could be contributing to you exceeding the 10 connection limit. To avoid using connection pooling you can set the POOLING=false connection string parameter. e.g. "Data Source=ASA 9.0 Sample;UID=DBA;PWD=SQL ;POOLING=FALSE;" This might add a bit of overhead to your connection time. S. Male wrote: We are using Adaptive Server Anywhere 9 for a website coded in ASP.Net (2003). We use services for each database. Each service is set as a "Personal Database Server" (there was a reason for this when we first set them up which escapes me now). We get an error when doing a long, iterative, process stating "Database server connection limit exceeded". The ASP.Net code closes the connection each iteration, but this error is still incurred. I notice on the website that a "Personal" database has a limit of 10, whereas a "Network" database has as per licence. I also noticed that the Microsoft Connection Pool could be an issue. Could you clarify what should be done to ensure this error does not occur? |
#6
| |||
| |||
|
|
Chris Are you saying that a "Network Database Server" is the type that we should be using then? NOTE: The personal server is not licensed for such use. The personal server is licensed for use in a standalone, single-user application. ASP.Net is not designed to be standalone and generally not a single user. -chris S. Male wrote: We are using Adaptive Server Anywhere 9 for a website coded in ASP.Net (2003). We use services for each database. Each service is set as a "Personal Database Server" (there was a reason for this when we first set them up which escapes me now). We get an error when doing a long, iterative, process stating "Database server connection limit exceeded". The ASP.Net code closes the connection each iteration, but this error is still incurred. I notice on the website that a "Personal" database has a limit of 10, whereas a "Network" database has as per licence. I also noticed that the Microsoft Connection Pool could be an issue. Could you clarify what should be done to ensure this error does not occur? |
Breck Carter - Blog: http://sqlanywhere.blogspot.com/
SQLA questions and answers: http://sqla.stackexchange.com
RisingRoad helps SQL Anywhere developers make better databases
http://www.risingroad.com/
Breck.Carter at gmail
#7
| |||
| |||
|
|
Kory You say "when using connection pooling". Does this means it's something we choose to use? Because we have not chosen to use this. Or is it (as I understand it) used anyway, hence the explicit "Pooling=False"? When using connection pooling, closing the connection will not actually close it, it is instead returned to the pool to be reused. This could be contributing to you exceeding the 10 connection limit. To avoid using connection pooling you can set the POOLING=false connection string parameter. e.g. "Data Source=ASA 9.0 Sample;UID=DBA;PWD=SQL ;POOLING=FALSE;" This might add a bit of overhead to your connection time. S. Male wrote: We are using Adaptive Server Anywhere 9 for a website coded in ASP.Net (2003). We use services for each database. Each service is set as a "Personal Database Server" (there was a reason for this when we first set them up which escapes me now). We get an error when doing a long, iterative, process stating "Database server connection limit exceeded". The ASP.Net code closes the connection each iteration, but this error is still incurred. I notice on the website that a "Personal" database has a limit of 10, whereas a "Network" database has as per licence. I also noticed that the Microsoft Connection Pool could be an issue. Could you clarify what should be done to ensure this error does not occur? |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.