Skip to main content
December 5, 2006
Question

Slow to no response

  • December 5, 2006
  • 3 replies
  • 823 views
I have an older box running Win2k with CF 5.0 SP 4 Enterprise, JRun 3.1 and MDAC 2.71.9030.9. Its my last box still running 5 that I was leaving alone for all my hosting customers who are running old apps and aren't willing to update. Over the past few months the box has degraded to ridiculous slowness when responding to ColdFusion requests. The non CF sites aren't having problems. End users regularly receive the following error when requesting a page:

ODBC Error Code = S1000 (General error)

[Microsoft][ODBC Microsoft Access Driver] Could not update; currently locked by user 'admin' on machine 'ROSEQUARTZ'.

Rosequartz is the name of the server.

When I look at the server.log I see lots of errors like:

"Error","832","12/05/06","15:00:50",,"Windows NT error number 109 occurred."
"Error","832","12/05/06","15:00:50",,"Error number 232 occurred attempting to close connection to web server."
"Error","832","12/05/06","15:00:50",,"Windows NT error number 232 occurred."
"Error","604","12/05/06","15:00:52",,"Error number 232 occurred while attempting to write the reply to the web server."
"Error","604","12/05/06","15:00:52",,"Windows NT error number 232 occurred."
"Error","604","12/05/06","15:00:52",,"Error number 232 occurred attempting to close connection to web server."
"Error","604","12/05/06","15:00:52",,"Windows NT error number 232 occurred."
"Error","604","12/05/06","15:00:53",,"Unable to write reply -- client browser stopped waiting for request. "
"Error","604","12/05/06","15:00:53",,"Windows NT error number 109 occurred."
"Error","604","12/05/06","15:00:53",,"Error number 232 occurred attempting to close connection to web server."

Rebooting does not even temporarily speed up the response rate. We have checked Windows, IIS, and everything else on this box and nothing appears to have a problem. Has anyone experienced something like this or have any advice?

Thanks,
J.
    This topic has been closed for replies.

    3 replies

    Participating Frequently
    December 15, 2006
    Inspiring
    December 14, 2006
    As a side note, owner A may have exceeded the 200,000 (or whatever low number it is) record limit of his Access db, thereby creating a lock preventing any new records. Database locks that never release create really long running threads on the server, tying up multiple threads over time and seriously degrading server performance.
    Inspiring
    December 14, 2006
    Did you check to see which version of MS Access the db files are now in? Here's a scenario for you: you host site for legacy clients on a legacy server and a legacy OS. One day site owner A decides to update his product db. The original product db was an Access '97 db, but owner A has finally upgraded to Office 2005. He, unknowingly, upgrades his Access db file to the latest and greatest when saving his changes, loads them onto your legacy system, and expects it to work with the same db drivers (for which none exist for your legacy system and his upgraded db).

    No offense to you (I know how expensive providing hosting can be) but it may be time for all parties involved to get on a proper upgrade path.