[
https://issues.apache.org/jira/browse/GEODE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542346#comment-16542346
]
Dan Smith commented on GEODE-5360:
----------------------------------
This was fixed by this commit
{noformat}
commit 035e7bb5261da510fea3321379383a86d6a1439b
Author: Dan Smith <upthewatersp...@apache.org>
Date: Thu Jun 28 11:55:06 2018 -0700
GEM-2031: Removing the use of shutdownNow from AcceptorImpl pools
Using shutdownNow interrupts the threads in these pools. These threads
may be doing IO on sockets, so shutdownNow will interrupt the threads
and potentially cause issues shutting down.
{noformat}
> 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
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
