[
https://issues.apache.org/jira/browse/TINKERPOP-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010764#comment-17010764
]
Dzmitry L commented on TINKERPOP-2328:
--------------------------------------
Another potential issue may happen if you decide to call "Dispose" on a client
while "PopulatePoolAsync" is active. "Dispose" closes all connections from the
pool, but does not stop "PopulatePoolAsync". So after "PopulatePoolAsync"
finish you will have unclosed connections.
> Do not close all connections if just one has became closed
> ----------------------------------------------------------
>
> Key: TINKERPOP-2328
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2328
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.4.4
> Reporter: Dzmitry L
> Priority: Major
>
> Current implementation of "ConnectionPool" closes all available connections
> if just one has became closed (is not opened)
> [https://github.com/apache/tinkerpop/blob/0b9eb170c93dd114f012cb63bfbd1c5a240e58f4/gremlin-dotnet/src/Gremlin.Net/Driver/ConnectionPool.cs#L154]
> what leads to "ServerUnavailableException"
> We could leave all remaining connections.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
