[
https://issues.apache.org/jira/browse/GEODE-10287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539655#comment-17539655
]
Jinmei Liao commented on GEODE-10287:
-------------------------------------
Oh, yeah, you are right. The test specifically blocks the operation and cause
the `waitForCurrentOperations` to wait forever, that's why the test hang. If we
close the distadvisor before the wait, then the wait is a no-op. then the test
succeeds.
> DistributedRegion.distributedRegionCleanup logic looks wrong
> ------------------------------------------------------------
>
> Key: GEODE-10287
> URL: https://issues.apache.org/jira/browse/GEODE-10287
> Project: Geode
> Issue Type: Bug
> Components: core
> Reporter: Darrel Schneider
> Assignee: Jinmei Liao
> Priority: Major
>
> DistributedRegion.distributedRegionCleanup does this: distAdvisor.close().
> Then a few lines later it calls "waitForCurrentOperations()". But
> waitForCurrentOperations uses the closed distAdvisor. Maybe it is okay to
> uses a closed distAdvisor but it seems better to call wait first and then
> close distAdvisor.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
