You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Isaac (JIRA)" <ji...@apache.org> on 2019/02/07 14:38:00 UTC
[jira] [Commented] (TINKERPOP-2155) Situation can occur that causes
infinite amount of connection to be opened, causing
System.Net.WebSockets.WebSocketException
[ https://issues.apache.org/jira/browse/TINKERPOP-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762718#comment-16762718 ]
Isaac commented on TINKERPOP-2155:
----------------------------------
Created PR: [https://github.com/apache/tinkerpop/pull/1057] to stop the bleeding
> Situation can occur that causes infinite amount of connection to be opened, causing System.Net.WebSockets.WebSocketException
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: TINKERPOP-2155
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2155
> Project: TinkerPop
> Issue Type: Bug
> Components: dotnet
> Affects Versions: 3.4.0
> Reporter: Isaac
> Priority: Critical
>
> In the tinkerpop/gremlin-dotnet/src/Gremlin.Net/Driver/ConnectionPool.cs, a bug exists where the connection count locking mechanism logic can create a situation that creates infinite amount of connections to be opened. My suspicion is that its within the while(true) loop within the EnsurePoolIsPopulatedAsync function.
>
> I cannot reliably recreate the issue, but since updating from 3.4.0-rc2 to 3.4.0, I've seen this issue happen several times, which cause our hosting environment to run out of socket connections and start throwing:
> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)