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. http://pastebin.com/wP8Xfrwf On Wednesday, September 12, 2012 9:20:10 AM UTC-5, Tom Evans wrote: > > On Wed, Sep 12, 2012 at 2:49 PM, Dane <daneg...@gmail.com <javascript:>> > 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 view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/SHH0MsPA8tQJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
