[
https://issues.apache.org/jira/browse/ARTEMIS-4789?focusedWorklogId=921465&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-921465
]
ASF GitHub Bot logged work on ARTEMIS-4789:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 31/May/24 02:07
Start Date: 31/May/24 02:07
Worklog Time Spent: 10m
Work Description: clebertsuconic opened a new pull request, #4950:
URL: https://github.com/apache/activemq-artemis/pull/4950
this is fixing PagingTest::testPagingStoreDestroyed(db=derby) (or any other
DB).
This could eventually also fail on journal.
The cleanup could act on a destroyed folder, and issue an IOException
stopping the server with this race.
You would need the server active cleaning messages while the queue is being
removed.
Issue Time Tracking
-------------------
Worklog Id: (was: 921465)
Remaining Estimate: 0h
Time Spent: 10m
> Page.destroy race with cleanup
> ------------------------------
>
> Key: ARTEMIS-4789
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4789
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.33.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Fix For: 2.34.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There's a rare race between Queue.destroy and cleanup.
> if the cleanup is called while depaging is still happening you might endup
> with a Critical IO exception as the storage folder is removed.
> This is the reason why testPagingStoreDestroyed(derby) was eventually failing.
> testPagingStoreDestroyed serves as the verification for this issue, as this
> is intended as the test fix.
--
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
