[
https://issues.apache.org/jira/browse/ARTEMIS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851195#comment-17851195
]
ASF subversion and git services commented on ARTEMIS-4789:
----------------------------------------------------------
Commit fa1c5c71738baf8016921364a834a722902d8e05 in activemq-artemis's branch
refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=fa1c5c7173 ]
ARTEMIS-4789 Page.destroy race with cleanup
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.
> 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: 0.5h
> 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
