[
https://issues.apache.org/jira/browse/GEODE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5360:
-----------------------------
Description: We saw a hang during close cache where a member was stuck
waiting for a reply. I tracked it down to the fact that AcceptorImpl.close was
calling shutdownNow on it's thread pools, and interrupted a
clientQueueInitialization thread in the middle of a GII. I believe this caused
a lost message due to GEODE-5358, resulting in a hang. (was: We saw a hang
during close cache where a member was stuck waiting for a reply. I tracked it
down to the fact that AcceptorImpl.close was calling shutdownNow on it's thread
pools, and interrupted a clientQueueInitialization thread in the middle of a
GII. I believe this caused a lost message due to GEODE-5348, resulting in a
hang.)
> AcceptorImpl.close calls shutdownNow, which interrupts threads
> --------------------------------------------------------------
>
> Key: GEODE-5360
> URL: https://issues.apache.org/jira/browse/GEODE-5360
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Reporter: Dan Smith
> Priority: Major
>
> We saw a hang during close cache where a member was stuck waiting for a
> reply. I tracked it down to the fact that AcceptorImpl.close was calling
> shutdownNow on it's thread pools, and interrupted a clientQueueInitialization
> thread in the middle of a GII. I believe this caused a lost message due to
> GEODE-5358, resulting in a hang.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
