Context Navigation

Changes between Initial Version and Version 1 of Ticket #22420, comment 18

initial	v1
1		I'm running ~~about~~ the same problem; it happens after a successful test run as well. More details: we're using Django 1.6 (though it happened in 1.5 as well) and Selenium tests with a `TransactionTestCase` and a `LiveServerThread` from Django. After every Selenium test run (in `fixture_teardown`) we're closing Selenium then joining the server thread,
	1	I'm running into the same problem; it happens after a successful test run as well. More details: we're using Django 1.6 (though it happened in 1.5 as well) and Selenium tests with a `TransactionTestCase` and a `LiveServerThread` from Django. After every Selenium test run (in `fixture_teardown`) we're closing Selenium then joining the server thread,
2	2
3	3	From what I could determine, `django.db.connections.all()` doesn't show any other connections after closing the thread; however `SELECT * from pg_stat_activity` sometimes reveals a second connection (reported as having done `COMMIT;` just before the fixture teardown). The second connection often lingers for half a minute. We're not using the `CONN_MAX_AGE` setting.