[
https://issues.apache.org/jira/browse/ARTEMIS-5349?focusedWorklogId=961659&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-961659
]
ASF GitHub Bot logged work on ARTEMIS-5349:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/25 18:21
Start Date: 13/Mar/25 18:21
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #5557:
URL:
https://github.com/apache/activemq-artemis/pull/5557#issuecomment-2722325824
> What's leaking?...
>
> I would recommend adding a test under ./leak-tests...
>
> It is using a pet library I created... you can write code like this:
>
> CheckLeak leak = new CheckLeak(); Assert.equals(0,
checkLeak.getInstances("your-leaking-class").length);
Bridges where leaking, such that on all configuration reloads, concurrency
number of new bridges where added each time and the previous ones where left
without management.
The effect would be an ever increasing amount of consumers connected to the
bridged queue that could not be closed, except from a broker restart.
Issue Time Tracking
-------------------
Worklog Id: (was: 961659)
Time Spent: 50m (was: 40m)
> Bridges with concurrency can leak
> ---------------------------------
>
> Key: ARTEMIS-5349
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5349
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This affects bridges whose configuration has been persisted. Simply adding
> persistence to the pre-existing test case captures this bug
--
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
