On Wed, Sep 12, 2012 at 2:49 PM, Dane <[email protected]> wrote: > After using django 1.3 for a while I upgraded to django 1.4 and started > noticing apache threads hanging indefinitely. I set a timeout to avoid > running out of threads, but it would be nice to know what is causing the > issue in the first place. > > Using an strace, I found that the threads are attempting to read from a > socket and are not doing anything after that. > > The apache logs were not helpful, but we did find the following stacktrace > in our mod_wsgi process:
The stacktrace doesn't look relevant tbh. How are you determining that you have hanging threads? Eg, is the scoreboard completely full? It would be easier to debug if you could capture a snapshot of the scoreboard whilst you think you are being affected. mod_status is your friend, turn "ExtendedStatus on". Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en.
