The detective work you have done is quite outstanding. Many people
don't bother and certainly don't document it.
Try adding this one line to your Apache configuration for mod_wsgi.
WSGIApplicationGroup %{GLOBAL}
The hanging of an application like that can be a third party extension
module which isn't written properly to work in a sub interpreter. That
statement forces mod_wsgi to run application in main interpreter just
like it would be with command line Python.
http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Python_Simplified_GIL_State_API
If that doesn't work, next thing you can try is:
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Extracting_Python_Stack_Traces
Graham
On 29 July 2011 10:42, gardsted <[email protected]> wrote:
> It's sort of a lenghty writeup, so I put it here:
> http://barskdata.net/files/investigate-wsgi.html
>
> But basically it is like this:
>
> application = cherrypy.Application(LazyInventory(), script_name=None,
> config=config)
>
> where class LazyInventory(object) is like this (manually indented
> here)
>
> @cherrypy.expose
> def index(self):
> print >> sys.stderr, 'index should redirect to dashboard'
> data = {
> 'redirect':"/dashboard",
> }
> # redirect to dashboard
> raise cherrypy.HTTPRedirect(data['redirect'])
>
> My index method never gets called - browser just says connecting
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/modwsgi?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
