[ https://issues.apache.org/jira/browse/TINKERPOP-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166439#comment-16166439 ]
ASF GitHub Bot commented on TINKERPOP-1766: ------------------------------------------- Github user jorgebay commented on the issue: https://github.com/apache/tinkerpop/pull/704 It's weird because 6a3fc39a912bec98707dd69d461955330627df10 was merged by @spmallette on master in 75502eef222b0dfc7aa83c2456ab319a9f9dd1a6 (he beat me to it because I was taking too long to do it) and this branch started in 98e4e1b8201f50e1f34458a82c20f2737aa6ae53, which is down the line. > 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 > > 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)