You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Florian Hockmann (JIRA)" <ji...@apache.org> on 2017/09/14 15:56:00 UTC

[jira] [Closed] (TINKERPOP-1766) Gremlin.Net: Closed connections should not be re-used

     [ https://issues.apache.org/jira/browse/TINKERPOP-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Hockmann closed TINKERPOP-1766.
---------------------------------------
    Resolution: Fixed

> Gremlin.Net: Closed connections should not be re-used 
> ------------------------------------------------------
>
>                 Key: TINKERPOP-1766
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1766
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: dotnet
>    Affects Versions: 3.3.0, 3.2.6
>            Reporter: Florian Hockmann
>             Fix For: 3.2.7, 3.3.1
>
>
> The driver of Gremlin.Net is kept very simle which holds especially true for the {{ConnectionPool}}. It simply returns every connection to its pool of usable connections that was {{disposed}} by the client. Unfortunately, this also applies in case the submit failed due to an already closed connection which means that the client will get the closed connection back from the {{ConnectionPool}} later and continues trying to submit messages over this closed connection.
> This can be fixed by checking whether the {{Connection}} is still open before adding it back to the {{ConnectionPool}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)