#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: Uncategorized | Version: 1.5
Severity: Normal | Resolution:
Keywords: uwsgi postgres | Triage Stage:
mysql idle connections | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
This is a bug in uWSGI, I've hit it in production too. Thanks for filing
this ticket.
Django < 1.5 didn't exhibit this behavior because it closed the database
connection earlier. But code could reopen the connection later on, before
the end of the request, in the case of streaming responses. That was a
bug, I fixed it, and I still think it's the right thing to do.
Since Django 1.5 provides explicit support for streaming responses, the
closing of the database connection must be performed after the content is
fully sent, ie. in `close()`.
I think the best we can do is document this bug of uWSGI in the deployment
docs and in the 1.5 release notes.
--
Ticket URL: <https://code.djangoproject.com/ticket/20537#comment:1>
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/063.1da97c7221c23a5a5986053d740448cd%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
