Database connection not closed
Bug #1231332 reported by
Michael Nelson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Software Center Agent |
Fix Released
|
Undecided
|
Michael Nelson | ||
Ubuntu Apps Directory |
Fix Committed
|
Undecided
|
Michael Nelson | ||
ubuntu-recommender |
Fix Committed
|
Undecided
|
Michael Nelson |
Bug Description
We are seeing hung connections from myapps, recommender and ubuntu-webcatalog, which is stopping the database compact from running.
The work-around was to kill those hung transactions and enable the compact to run, but then the apps don't get a new db connection and continue trying to use the old one [1].
Related RT: 64831
[1] https:/
Changed in software-center-agent: | |
status: | New → In Progress |
assignee: | nobody → Michael Nelson (michael.nelson) |
Changed in software-center-agent: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Regarding the hung transactions, see this note from the Django 1.5 release notes [1]. We should check our wsgi middleware (oops?) and ensure it's explicitly closing the response object.
[1] https:/ /docs.djangopro ject.com/ en/dev/ releases/ 1.5/#request- finished- signal