[jira] [Comment Edited] (ARTEMIS-3305) compatibility tests dont work on Java 16+

["Clebert Suconic (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552901#comment-17552901 ] 

Clebert Suconic edited comment on ARTEMIS-3305 at 6/10/22 6:45 PM:
-------------------------------------------------------------------

[~robbie]the memory high usage happens because there are leaks preventing the classLoading from being released.

Some of the leaks were client threads from the thread pooling. 


I did clear some of it.. but there seems to be other leaks at the Groovy layer.


They don't seem to block the tests running now. at least now the tests are runnable. 

I did clear some of the leaks so perhaps that will help with execution as well.


I will close the issue once the PR I sent is merged


was (Author: clebertsuconic):
[~robbie]the memory consumption happens because there are leaks preventing the classLoading from being released.

Some of the leaks were client threads from the thread pooling. 


I did clear some of it.. but there seems to be other leaks at the Groovy layer.


They don't seem to block the tests running now. at least now the tests are runnable. 

I did clear some of the leaks so perhaps that will help with execution as well.


I will close the issue once the PR I sent is merged

> compatibility tests dont work on Java 16+
> -----------------------------------------
>
>                 Key: ARTEMIS-3305
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3305
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 2.18.0
>            Reporter: Robbie Gemmell
>            Assignee: Clebert Suconic
>            Priority: Major
>
> ARTEMIS-3296 enabled the build to run on Java 16 and got the PR build passing there. It disabled running the tests in the compatibility-tests module to achieve this though.
> In its current state, the tests look to fail primarily due to an older groovy 2.5.x version, however upgrading this to the 3.0.8 release wasnt enough to get things working, with the tests progressing but seeming to get into an infinite-reconnect scenario where connection was failing and reporting a client-server version mismatch, and eventually OOM errors etc as well.
> Work is needed to see whether other changes, such as adding specific module exports, can get the compatibility tests running on Java 16+. Its always possible some of the previous client/server versions they use wont actually run on 16, so perhaps even only a subset can.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)