[
https://issues.apache.org/jira/browse/TINKERPOP-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008858#comment-17008858
]
Florian Hockmann commented on TINKERPOP-2328:
---------------------------------------------
[~idzmitry] Did you encounter a concrete scenario where just one connection was
closed, but the others could still be used?
The reasoning for closing all connections if just one is detected as closed is
that the server is expected to be not reachable at all in which case the other
connections are also dead, it just might not have been noticed for them yet.
Apart from that, a fix for TINKERPOP-2288 should also avoid that an exception
gets thrown here if the server is indeed reachable as the connections should
then be repaired / replaced in the background automatically.
> 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)
