#20537: `request_finished` signal not being called with Django 1.5 and uWSGI <
1.2.6(?)
-------------------------+-------------------------------------------------
Reporter: jaap3 | Owner: nobody
Type: Bug | Status: new
Component: | Version: 1.5
Uncategorized | Keywords: uwsgi postgres mysql idle
Severity: Normal | connections
Triage Stage: | Has patch: 0
Unreviewed | UI/UX: 0
Easy pickings: 0 |
-------------------------+-------------------------------------------------
As discovered on the django-users mailinglist in the thread
[https://groups.google.com/d/msg/django-users/FxTD5M0x-G8/rQZdOgVcDYQJ
request_finished signal not being called with Django 1.5.1 with uwsgi]
The version of uWSGI in the Ubuntu/Debian apt repositories (1.0.3) doesn't
call `close` on the wsgi application, this in turn causes the
`request_finished` signal to never fire resulting in open database
connections.
According to [http://blog.dscpl.com.au/2012/10/obligations-for-calling-
close-on.html this blogpost] uWSGI >= 1.2.6 should be the first version of
uWSGI that supports the expected behavior. But the same blogpost warns
about other wsgi middleware potentially misbehaving.
I'm wondering why Django < 1.5 didn't show this behavior and what the best
course for Django regarding this issue is.
Should there be a warning in the docs about the minimum required uWSGI
version? Or should the previous behavior be restored somehow?
--
Ticket URL: <https://code.djangoproject.com/ticket/20537>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.83cfd1cc5007a68afbddf36e42283bdd%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
