[
https://issues.apache.org/jira/browse/GEODE-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127594#comment-16127594
]
ASF GitHub Bot commented on GEODE-3416:
---------------------------------------
Github user hiteshk25 commented on a diff in the pull request:
https://github.com/apache/geode/pull/702#discussion_r133249141
--- Diff:
geode-core/src/main/java/org/apache/geode/internal/tcp/ConnectionTable.java ---
@@ -929,10 +929,6 @@ protected void removeEndpoint(DistributedMember
memberID, String reason,
owner.getDM().getMembershipManager().getShutdownCause());
}
}
-
- if (remoteAddress != null) {
-
this.socketCloser.releaseResourcesForAddress(remoteAddress.toString());
- }
--- End diff --
This doesn't require??
> Reduce blocking for SocketCloser.asyncClose
> --------------------------------------------
>
> Key: GEODE-3416
> URL: https://issues.apache.org/jira/browse/GEODE-3416
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.2.1
> Reporter: Udo Kohlmeyer
> Assignee: Udo Kohlmeyer
> Fix For: 1.3.0
>
>
> In the SocketCloser.asyncClose method, there is a synchronization block
> around at HashMap. This synchronization will cause an effective
> single-threaded processing capability when closing sockets. this effect
> becomes more evident with a high number of clients.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
