Hi Derek, Thanks for replying, I had checked those but the last entry was months old, so that was a dead end.
I finally got web2py running on Apache, though it took me till 5 am :-) (ps: if anyone else plans on attempting to install Apache on Windows against MSSQL, I'm happy to help out or write a tutorial, it wasn't straightforward! Feel free to pm me) I left both the rocket and the apache web2py installs live running on separate servers (pointing to same database) and advised the users to work on both. When I checked after a few hours, the rocket one had become unresponsive, and apache was still running fine. I think the problem is something to do with to the server being overloaded, and perhaps ajax calls time out and holding locks on the sessions files, causing the whole thing to become unresponsive. There were multiple threads interacting with the same session files judging from the debugger... If anyone would like me to do more investigation on this, I'm happy to help so long as you tell me where to look. Apache also caused a rather funny issue... A set of ajax calls which were meant to run synchronously (because of "async: false" flag) was failing to complete before page reload, whereas it always did before, leading me to think Apache was not running it synchronously as instructed. What I think is happening is that the ajax call never ran synchronously in the first place (it's in a jQuery.each() loop) but on rocket it always finished on time before the page reload, and apache seems to reload way faster so caught me out. Word to the wise: check any assumptions you make about ajax running synchronously or not, especially as async: false is deprecated in jQuery 1.8. On Wed, Nov 6, 2013 at 5:28 PM, Derek <sp1d...@gmail.com> wrote: > Check the logs, find the last line in the log - that's probably what > caused the freeze. Check your logging.conf to find out where the logs are > kept. > > > On Tuesday, November 5, 2013 1:59:43 PM UTC-7, Andrew Buchan wrote: >> >> Update: >> >> I made a copy of the web2py installation on a new server (still pointing >> to old database) and eventually got it set it up as a service but it >> still freezes with no errors in web2py or in the event manager... >> >> I'm pretty sure it's a programming error on my part somewhere or a >> migration issue, but I need to be able to find out what it is!!! (people >> are getting tetchy...) >> >> I went back to the original server and tried debugging using winpdb, and >> it seems web2py gets stuck in a perpetual loop. When I pause, it tends to >> stop in the "run" or "listen" methods in rocket.py, or "accept" in >> socket.py (python installation dir), so the thread is running, just in a >> loop and not responding to new requests... >> >> I'm thinking of putting the server onto apache to see if it behaves any >> differently, but if anyone has any bright suggestions on what I can do to >> find out what's going, I'm all ears :-) >> >> >> >> >> >> -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to a topic in the > Google Groups "web2py-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/web2py/PEC1uLfzlrU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > web2py+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
