GitHub user spmallette opened a pull request:
https://github.com/apache/tinkerpop/pull/367
TINKERPOP-1350 was never quite fixed in 3.1.3.
Unfortunately, more testing revealed that the fix for the problem was only
masked by the changes in 3.1.3.
Changed response encoding to not use the session executor when the session
has an error condition it is trying to serialize. This should be fine as there
is no need to serialized an error condition as part of a transaction and thus
no need to have the session thread to do it. That in turn frees up the worker
executor to serialize and cancel long run jobs in the session. Removed
recommendations for submitting parallel requests on a session from docs.
Works in full with `mvn clean install && mvn verify -pl gremlin-server
-DskipIntegrationTests=false`
VOTE +1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/tinkerpop TINKERPOP-1350
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/367.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 #367
----
commit 57ef449ded52e5c11072e7a626eebcfcc13889c4
Author: Stephen Mallette <sp...@genoprime.com>
Date: 2016-08-02T19:59:19Z
TINKERPOP-1350 was never quite fixed in 3.1.3.
Changed response encoding to not use the session executor when the session
has an error condition it is trying to serialize. This should be fine as there
is no need to serialized an error condition as part of a transaction and thus
no need to have the session thread to do it. That in turn frees up the worker
executor to serialize and cancel long run jobs in the session. Removed
recommendations for submitting parallel requests on a session from docs.
----
---
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.
---
