I have an app running under mod_wsgi on a real apache2 instance which takes a LONG time to process requests. This is due to huge quantity of database operations in a single transaction and is fine for our application requirements. Due to database locking both the original request (and other requests) have to wait. These fail with gateway timeouts. To resolve this I simply increased the apache2.conf Timeout setting to the worst case number of seconds.
I now have moved to a docker environment using Graham Dumpleton's excellent mod_wsgi-express onbuild container. This uses defaults for apache2 and as a result I am back with the same errors. I have spent a morning wandering around the internet and cannot find out the "correct" way to increased the Timeout to the value I require. Clearly I could update the prepared httpd config file after it is created but this doesnt seem right. The mod_wsgi-express start-server help talks about various timeouts but I never needed to tweak anything on my "real" instance in this area. Are some of these relevant to my issue? I dont want to randomly start changing things. Some comments (eg Graham's blogs) indicate httpd settings propagate through (via SERVER_ARGS) and the mod_wsgi-start-server script shows it can be set up in a .whiskey/server_args file (but no required format given). The source code for mod_wsg-express is rather opaque in how it starts the httpd instance and under what environment or option switch settings. Please can anyone help? Thanks -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
