Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Auto Closed
-
0.12
-
None
-
None
Description
Several (but not all) the federation tests leak connection objects. This causes the connections and hence the threads behind them to remain active beyond the life of the test, and are cleaned up only when the entire test set completes. This test set is short enough that there is currently no side-effect, but if the test set is lengthened, then tests could potentially fail because there are no more handles available for threads. (In Linux, the default is 1024 handles per user.)
By observing calls to qpid.Connection.start() and qpid.Connection.close(), tests can be seen where start() is called for a connection, but no matching close() exists. Using this technique, the following tests were observed to leak connections (with the number of leaked connections):
federation.FederationTests.test_dynamic_direct (1)
federation.FederationTests.test_dynamic_direct_reorigin (1)
federation.FederationTests.test_dynamic_fanout (1)
federation.FederationTests.test_dynamic_headers_all (1)
federation.FederationTests.test_dynamic_headers_any (1)
federation.FederationTests.test_dynamic_headers_reorigin (1)
federation.FederationTests.test_dynamic_headers_reorigin_xml (1)
federation.FederationTests.test_dynamic_headers_unbind (1)
federation.FederationTests.test_dynamic_headers_unbind_xml (1)
federation.FederationTests.test_dynamic_headers_xml (1)
federation.FederationTests.test_dynamic_topic (1)
federation.FederationTests.test_dynamic_topic_nodup (1)
federation.FederationTests.test_dynamic_topic_reorigin (1)
federation.FederationTests.test_pull_from_exchange (1)
federation.FederationTests.test_pull_from_queue (1)
federation.FederationTests.test_push_to_exchange (1)
federation.FederationTests.test_tracing (1)
federation.FederationTests.test_tracing_automatic (1)