I'm running a python app using mod-wsgi-docker, as a replacement for using 
it on a manually configured server.

The application is flask/sqlalchemy/mysql, and it's working fine, except I 
see occasional errors that seem
to be sqlalchemy complained that an existing transaction needs to be rolled 
back. It's just a guess, but I
wondering if this due to new requests being handled by an existing process 
that has handled previous
requests that have left state lying around, like unclosed sessions, that 
are causing new requests to fail.

While no doubt I should find and fix where state is not cleaned up - I'd be 
keen to not be exposed to problems
like this. And I think I could do this by configuring each request to be 
handled in a separate process.

Is is easy to do this? I've been only using the default setup, which seems 
to be 1 process, 5 threads.
How can I change this to, say, 5 processes, each single threaded, and would 
that help?  Or would it
make no difference because the same processes remain used for multiple 
requests. And if that's the
case, is there a way to have a new process started and finished for each 


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 modwsgi+unsubscr...@googlegroups.com.
To post to this group, send email to modwsgi@googlegroups.com.
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to