Here is a more specific error as I just hit this issue again (paraphrased):
Cannot create table xxxx because it already exists in the database. I fixed the error but had to restart the web2py service to get the site to respond after the correction was made. On Monday, August 20, 2012 12:49:34 PM UTC-6, Niphlod wrote: > > it's pretty obscure the way you describe those errors: "certain DB errors" > are what ? unique constraints not respected? db migrations ? heavy > complicated queries ? file uploads ? > > On Monday, August 20, 2012 6:35:10 PM UTC+2, David Rager wrote: >> >> Hey all - we have a persistent issue in our staging environment where our >> site will hang after certain DB errors. It feels like a transaction is >> hanging on the DB but am still confused as we instruct rocket to use >> multiple threads, so am unsure why it would block other requests. >> >> Is it possible that the rocket deploy on Windows is not the idea >> deployment? Should we switch to apache? >> >> I think I found an old, similar issue where an auto_commit was added to >> the dal object instantiation but am not clear on the implementation or the >> side effects. >> >> Appreciate any ides. On our prod environment where DB errors have mostly >> been knocked down we don't see this type of behavior, but the fear is it >> will show up at some point. >> >> Thanks! >> > --
