[
https://issues.apache.org/jira/browse/AMQ-9861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057926#comment-18057926
]
ASF subversion and git services commented on AMQ-9861:
------------------------------------------------------
Commit a8fa4b09b54eaca06d106e754796798bd88e21e9 in activemq's branch
refs/heads/main from Jean-Louis Monteiro
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a8fa4b09b5 ]
[AMQ-9860] [AMQ-9861] connection async exception handling and activemq pool
tests connection leaks to other tests (#1657)
* [AMQ-9861] activemq-pool tests have resource leaks causing test interference
activemq-pool tests use default broker name causing BrokerRegistry collisions
Missing waitUntilStopped() after broker.stop() in tests
* [AMQ-9860] Refactor async exception handling to improve resource management
and prevent task execution on closed connections
* Increase timeout for exception event propagation in
ConnectionFailureEvictsFromPoolTest
* Refactor PooledConnectionFactory to remove AutoCloseable implementation and
improve resource management in tests
> activemq-pool tests leaking connections and reusing forks
> ---------------------------------------------------------
>
> Key: AMQ-9861
> URL: https://issues.apache.org/jira/browse/AMQ-9861
> Project: ActiveMQ
> Issue Type: Test
> Components: Pool
> Reporter: Jean-Louis Monteiro
> Priority: Major
> Fix For: 6.3.0
>
>
> Several activemq-pool tests:
> - Never called PooledConnectionFactory.stop(), leaking internal connection
> pools
> - Used the default broker name (localhost) in vm:// URIs, causing
> BrokerRegistry collisions when tests ran in the same fork
> - Did not call broker.waitUntilStopped() after broker.stop(), leaving
> brokers partially alive for subsequent tests
> - Reused forks, allowing leaked resources from one test to interfere with
> the next
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
