Hi y'all,
About 6 months ago I was a hosting a site that started to pick up a fair amount of traffic...not too hot, maybe 500 visitors / day.
However, the Access database I'm using seemed to randomly 'lock up' giving the error (I'm paraphrasing from memory):
"too many client tasks"
The database would then *stay locked* for 1-3 hours, which needless to say, was no good at all.
Has anyone else had this? Does anyone actually know what it means?
From my research I've found that it happens to ASP and PHP users when they fail to close the database connection properly (since they have to close it manually, I can see how this error can occur).
The reason I'm asking is that I'm going to start this site up again and I'm worried that this is going to continue.
Would anyone suggest that CFTRANSACTION might be a good way around it? If I can single thread all database transactions (or at least manage them somehow), perhaps that will avoid the error.
Lastly, does anyone know whether this is a peril of being on a host with multiple websites? Is this lock 'database oriented' or ODBC oriented? If the latter, then perhaps it is an issue with having lots of people using ODBC on the same server.
Anyway, it was a cause of continual frustration and will, I suspect, continue to be, unless the greater minds at Tek-Tips can possibly help.
Thanks in advance,
Kendo.
PS. I'm a fairly experienced coldfusion and web programmer. The database itself and the code is sound - I'm reasonably confident of that. It does seem to be an error caused by increased thru-put.
PPS. I cannot afford hosting with SQL Server backend.
About 6 months ago I was a hosting a site that started to pick up a fair amount of traffic...not too hot, maybe 500 visitors / day.
However, the Access database I'm using seemed to randomly 'lock up' giving the error (I'm paraphrasing from memory):
"too many client tasks"
The database would then *stay locked* for 1-3 hours, which needless to say, was no good at all.
Has anyone else had this? Does anyone actually know what it means?
From my research I've found that it happens to ASP and PHP users when they fail to close the database connection properly (since they have to close it manually, I can see how this error can occur).
The reason I'm asking is that I'm going to start this site up again and I'm worried that this is going to continue.
Would anyone suggest that CFTRANSACTION might be a good way around it? If I can single thread all database transactions (or at least manage them somehow), perhaps that will avoid the error.
Lastly, does anyone know whether this is a peril of being on a host with multiple websites? Is this lock 'database oriented' or ODBC oriented? If the latter, then perhaps it is an issue with having lots of people using ODBC on the same server.
Anyway, it was a cause of continual frustration and will, I suspect, continue to be, unless the greater minds at Tek-Tips can possibly help.
Thanks in advance,
Kendo.
PS. I'm a fairly experienced coldfusion and web programmer. The database itself and the code is sound - I'm reasonably confident of that. It does seem to be an error caused by increased thru-put.
PPS. I cannot afford hosting with SQL Server backend.