Further update: Apache did finally crash, with the following message: "Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting" I've bumped that up to 500, and there are less than that number of users on the system (although I understand there will be more than one connection fired off per user/session). But it crashed/became unresponsive again with no error message! I added mod_status to see what's going on, and it seems there are loads of requests being sent to which never exit, and I can't tell where these are being fired from as they don't indicate which virtualhost they came from (and no url mapping). I'm waiting for approval to join apachelounge to ask over there, but thought I'd ask here if anyone had any information on how web2py uses/creates requests/threads in apache, and how it could be that apache becomes unresponsive after a while. I'm not even sure it is running out of workerthreads (I thought servers queued requests till threads became available specifically so they wouldn't crash under heavy load).
Also, I leave sessions alone, but should I be clearing them? Also also, I updated to the latest version of web2py and it seems someone left a print statement in SQLFORM.grid() which prints every row! (Line 2373 in sqlhtml.py) I presume that if I were running that as a windows service on rocket it would crash the moment you displayed a grid... > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
