You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barrett Oglesby (Jira)" <ji...@apache.org> on 2021/12/07 00:21:00 UTC
[jira] [Resolved] (GEODE-9865) ConnectionManagerImpl forceCreateConnection to a specific server increments the count regardless whether the connection is successful
[ https://issues.apache.org/jira/browse/GEODE-9865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barrett Oglesby resolved GEODE-9865.
------------------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
> ConnectionManagerImpl forceCreateConnection to a specific server increments the count regardless whether the connection is successful
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-9865
> URL: https://issues.apache.org/jira/browse/GEODE-9865
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Affects Versions: 1.14.0
> Reporter: Barrett Oglesby
> Assignee: Barrett Oglesby
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> *ConnectionManagerImpl forceCreateConnection* does:
> {noformat}
> private PooledConnection forceCreateConnection(ServerLocation serverLocation)
> throws ServerRefusedConnectionException, ServerOperationException {
> connectionAccounting.create();
> try {
> return createPooledConnection(serverLocation);
> } catch (GemFireSecurityException e) {
> throw new ServerOperationException(e);
> }
> }{noformat}
> The call to *connectionAccounting.create()* increments the count. If *createPooledConnection* is unsuccessful, the count is not decremented. This causes the client to think there are more connections than there actually are.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)