GitHub user spmallette opened a pull request:
https://github.com/apache/tinkerpop/pull/442
TINKERPOP-1467 Corrected a number of problems in close() operations for the
driver [master]
https://issues.apache.org/jira/browse/TINKERPOP-1467
This work was from `tp31` and was pretty heavily conflicted so I decided on
a separate PR. Please see #441 for more information.
VOTE +1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/tinkerpop TINKERPOP-1467-master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/442.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #442
----
commit 934054f83a344ba32db3bcb8617c61340e2087a5
Author: Stephen Mallette <[email protected]>
Date: 2016-09-28T15:06:14Z
Corrected a number of problems in close() operations for the driver.
This was more of a commit than I wanted for tp31, but close() was really
messed up. Fixed a number of race conditions and other logic that would allow
the driver to hang on close. Also made it so that the Cluster makes an attempt
to clean up any Client instances that it spawns.
commit 6c84a71f5b50ba9e8a96b8ec766f26f1c8132b72
Author: Stephen Mallette <[email protected]>
Date: 2016-09-28T18:05:27Z
Merge remote-tracking branch 'origin/TINKERPOP-1467' into
TINKERPOP-1467-master
Conflicts:
CHANGELOG.asciidoc
gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/Channelizer.java
gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/Client.java
gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/Cluster.java
gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/Connection.java
gremlin-server/src/test/java/org/apache/tinkerpop/gremlin/server/GremlinDriverIntegrateTest.java
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
