[ 
https://issues.apache.org/jira/browse/ARTEMIS-4161?focusedWorklogId=845954&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-845954
 ]

ASF GitHub Bot logged work on ARTEMIS-4161:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Feb/23 17:22
            Start Date: 16/Feb/23 17:22
    Worklog Time Spent: 10m 
      Work Description: gemmellr commented on code in PR #4363:
URL: https://github.com/apache/activemq-artemis/pull/4363#discussion_r1108798577


##########
artemis-server/src/test/java/org/apache/activemq/artemis/tests/util/ActiveMQTestBase.java:
##########
@@ -251,6 +251,9 @@ public void runAfter() {
    }
 
 
+   protected void clearServers() {

Review Comment:
   Believe its used in the new test which subclasses this (I also thought it 
was unused initially)





Issue Time Tracking
-------------------

    Worklog Id:     (was: 845954)
    Time Spent: 5h 20m  (was: 5h 10m)

> AMQP and OpenWire have a few Leaks during open and close connections
> --------------------------------------------------------------------
>
>                 Key: ARTEMIS-4161
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4161
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.28.0
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.29.0
>
>          Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> OpenWire and AMQP are leaking objects in the following scenarios:
> AMQP:
> - Open Transactions, open connections, close connections, commit, send
> It appears these leaks are sustained as long as you keep closing and opening 
> sessions.
> OpenWire:
> - The leak here is not as critical as in AMQP, but a short term leak was 
> found while investigating the AMQP issue. (the AMQP connection would be 
> released after a TTL Timeout).
> To Validate this, I'm creating a new test suite:
> ./tests/leak-tests
> Which will use https://github.com/check-leak/check-leak to validate the 
> survival of these objects.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to