Re: Hung apache threads after upgrading to django 1.4

40 views
Skip to first unread message

Tom Evans

unread,
Sep 12, 2012, 10:19:42 AM9/12/12
to django...@googlegroups.com
On Wed, Sep 12, 2012 at 2:49 PM, Dane <daneg...@gmail.com> 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

Dane

unread,
Sep 13, 2012, 1:29:01 PM9/13/12
to django...@googlegroups.com, teva...@googlemail.com
We have extended status on.  Here is a link to our full status output.  This does not occur consistently, but under high traffic we see an increasing amount of occurrences.

I appreciate the help.

Reply all
Reply to author
Forward
0 new messages