[jira] [Commented] (ARTEMIS-4250) ShutdownOnCriticalIOErrorMoveNextTest failing

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-4250:
----------------------------------------------------------

Commit 0eefc38d9355e407be51cb397fef7c2f704ae330 in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0eefc38d93 ]

ARTEMIS-4250 Spawning VM to avoid thread leaking on ShutdownOnCriticalIOErrorMoveNextTest


> ShutdownOnCriticalIOErrorMoveNextTest failing
> ---------------------------------------------
>
>                 Key: ARTEMIS-4250
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4250
>             Project: ActiveMQ Artemis
>          Issue Type: Test
>    Affects Versions: 2.28.0
>            Reporter: Clebert Suconic
>            Priority: Major
>             Fix For: 2.29.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> ShutdownOnCriticalIOErrorMoveNextTest will simulate an IO failure, and some of the Executors are not being cleaned.
> This is an odd situation that would happen when the VM was coming down anyway. So the test should really use a spawned VM.
> The test is leaking threads, and spawning a VM would avoid these issues.



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