[
https://issues.apache.org/jira/browse/ARTEMIS-4526?focusedWorklogId=894089&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-894089
]
ASF GitHub Bot logged work on ARTEMIS-4526:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 05/Dec/23 15:14
Start Date: 05/Dec/23 15:14
Worklog Time Spent: 10m
Work Description: clebertsuconic merged PR #4703:
URL: https://github.com/apache/activemq-artemis/pull/4703
Issue Time Tracking
-------------------
Worklog Id: (was: 894089)
Time Spent: 20m (was: 10m)
> Move ShutdownOnCriticalIOErrorMoveNextTest into Isolated tests
> --------------------------------------------------------------
>
> Key: ARTEMIS-4526
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4526
> Project: ActiveMQ Artemis
> Issue Type: Test
> Affects Versions: 2.31.2
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ShutdownOnCriticalIOErrorMoveNextTest was actually my "inspiration" to have
> created the isolated tests module in the first place, so it would be
> reasonable to move it there as well.
> the issue comes down to the test simulating a server failure where the server
> would go down abruptly causing the VM to drop / exit. In this test the nature
> of failure is leaving a partial shutdown where server executors are still
> hanging around causing a cascade leak of server pools still running.
> So it is completely expected to have these threads "leaking". Hence this test
> should be moved into the isolated-tests.
> there is no semantic / server change as part of this task. It's just moving a
> test to a better place.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
