#35672: Using database connection pooling raises PoolTimeout after a while
-------------------------------------+-------------------------------------
Reporter: André S. Hansen | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Florian Apolloner (added)
* resolution: => needsinfo
* status: new => closed
Comment:
Hi Andre, I think we need more information to understand whether/where
Django is at fault here
I believe you have this error because the connection pool is full, this
could mean that Django is not closing connections after using them. For us
to be able to identify where this is happening, can you share a minimal
Django project and steps to reproduce?
--
Ticket URL: <https://code.djangoproject.com/ticket/35672#comment:2>
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/010701914aa5d5d9-9bc080cf-f426-4be9-90d7-813b59f953ef-000000%40eu-central-1.amazonses.com.
