#35059: ASGI server leaves stale DB connections
-------------------------------------+-------------------------------------
Reporter: James Thorniley | Owner: James
| Thorniley
Type: Bug | Status: closed
Component: HTTP handling | Version: 5.0
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia <124304+nessita@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"11393ab1316f973c5fbb534305750740d909b4e4" 11393ab]:
{{{#!CommitTicketReference repository=""
revision="11393ab1316f973c5fbb534305750740d909b4e4"
Fixed #35059 -- Ensured that ASGIHandler always sends the request_finished
signal.
Prior to this work, when async tasks that process the request are
cancelled due
to receiving an early "http.disconnect" ASGI message, the request_finished
signal was not being sent, potentially leading to resource leaks (such as
database connections).
This branch ensures that the request_finished signal is sent even in the
case
of early termination of the response.
Regression in 64cea1e48f285ea2162c669208d95188b32bbc82.
Co-authored-by: Natalia <[email protected]>
Co-authored-by: Carlton Gibson <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35059#comment:17>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018d609ecf29-15a55995-7d4e-4b7f-b8a2-978b86290f19-000000%40eu-central-1.amazonses.com.
