Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database connections left open if forming the web response fails #2877

Closed
droyad opened this issue Nov 1, 2016 · 3 comments
Closed

Database connections left open if forming the web response fails #2877

droyad opened this issue Nov 1, 2016 · 3 comments
Assignees
Milestone

Comments

@droyad
Copy link
Contributor

droyad commented Nov 1, 2016

If a web request fails in a response filter, the request lifecycle does not get disposed, leaving database connections open. The server also does not close the tcp connection.

This can be triggered by an invalid accept header.

@droyad droyad closed this as completed Nov 1, 2016
@octoreleasebot octoreleasebot added this to the 3.5.1 milestone Nov 1, 2016
@octoreleasebot
Copy link

Release Note: Closed database and network connections when an error occurs formatting the response

@droyad droyad modified the milestones: 3.5.0, 3.5.1 Nov 1, 2016
@droyad
Copy link
Contributor Author

droyad commented Nov 29, 2016

This issue may present itself in the logs with an error message The timeout period elapsed prior to obtaining a connection from the pool

@lock
Copy link

lock bot commented Nov 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants