[
https://issues.apache.org/jira/browse/ARTEMIS-5349?focusedWorklogId=961657&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-961657
]
ASF GitHub Bot logged work on ARTEMIS-5349:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Mar/25 18:01
Start Date: 13/Mar/25 18:01
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #5557:
URL:
https://github.com/apache/activemq-artemis/pull/5557#issuecomment-2722266048
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);
Issue Time Tracking
-------------------
Worklog Id: (was: 961657)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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
