GitHub user spmallette opened a pull request:

    https://github.com/apache/incubator-tinkerpop/pull/252

    TINKERPOP-1184 Fixed bug where session close was happening an extra time.

    https://issues.apache.org/jira/browse/TINKERPOP-1184
    
    If a session was closed explicitly by the client, the scheduled job to 
close the session on expiration was not being cancelled leading to a second 
closing. The second closing really wasn't doing anything "bad" but it did 
generate extra logging that was confusing if the user had expected the session 
to already be closed.  Refactored some of the session "kill" operations to make 
them a bit more thread safe.
    
    Tested with ` mvn clean install -DskipTests && mvn verify -pl 
gremlin-server -DskipIntegrationTests=false -DincludeNeo4j`
    
    VOTE +1

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/incubator-tinkerpop TINKERPOP-1184

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-tinkerpop/pull/252.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 #252
    
----
commit 5e19fd65376b2697d1fc423c39fa51e8fa11d7b2
Author: Stephen Mallette <sp...@genoprime.com>
Date:   2016-03-04T13:43:38Z

    Fixed bug where session close was happening an extra time.
    
    If a session was closed explicitly by the client, the scheduled job to 
close the session on expiration was not being cancelled leading to a second 
closing. The second closing really wasn't doing anything "bad" but it did 
generate extra logging that was confusing if the user had expected the session 
to already be closed.  Refactored some of the session "kill" operations to make 
them a bit more thread safe.

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to