[
https://issues.apache.org/jira/browse/GEODE-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052653#comment-17052653
]
ASF subversion and git services commented on GEODE-7832:
--------------------------------------------------------
Commit 2a3e09f2da4793d08d1124b5d5e656285295937d in geode's branch
refs/heads/feature/GEODE-7665 from Juan José Ramos
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2a3e09f ]
GEODE-7832: Remove Connection Semaphores (#4754)
Removed the semaphores and related methods from DirectChannel and
Connection classes. They were used to constrain messaging when some
undocumented system properties were set.
> Remove connection "send semaphores" from DirectChannel
> ------------------------------------------------------
>
> Key: GEODE-7832
> URL: https://issues.apache.org/jira/browse/GEODE-7832
> Project: Geode
> Issue Type: Improvement
> Components: membership
> Reporter: Bruce J Schuchardt
> Assignee: Juan Ramos
> Priority: Major
> Labels: GeodeCommons
> Fix For: 1.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Remove the acquiredSendSemaphore/acquireGroupSendSemaphore and related
> methods from DirectChannel/TCPConduit code. Connection.isReaderThread() and
> associated makeReaderThread() methods can also be deleted because they're
> only used by the semaphore code.
> These semaphores only constrain messaging if you set a couple of undocumented
> system properties, p2p.maxGroupSenders and p2p.maxConnectionSenders to some
> small value. These are (MAX_INT / 2) by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
