Hi Jim,

I've typically seen this error in my applications when I've done something
horribly wrong and ime it's usually accompanied by the cfserver service
restarting. It's possible that it could be related to locking, although
locking is typically not related to datasource issues ( although I've heard
of it being used as a workaround for certain problems with MS Access ) and
even when it is a database problem, you'll usually just get odbc errors
rather than big-time cf server problems...

It might be related to unlocked data manipulation in the application or more
often session scopes... and unfortunately being on a shared server, it'd be
difficult to say whether going through all of your own code and making sure
all of your own stuff is locked would even solve the problem. Personally I
think it'd be nice to see the hosting companies turning full-checking on on
their shared servers, but for various reasons ( loss of performance, time on
the phone with customers explaining locking, etc... ) it just doesn't happen
that way.

In any event, if you're using session, application or server ( I'd stay away
from these on a shared server ) variables I would probably _start_ by making
sure they're all locked and then if it continues I'd consider finding
another host if it's bothersome enough.

Wish I could provide more solid answers for you,

Isaac

www.turnkey.to
954-776-0046

______________________________________________________________________
Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to