[
https://issues.apache.org/jira/browse/TINKERPOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17826993#comment-17826993
]
ASF GitHub Bot commented on TINKERPOP-3063:
-------------------------------------------
FlorianHockmann opened a new pull request, #2522:
URL: https://github.com/apache/tinkerpop/pull/2522
https://issues.apache.org/jira/browse/TINKERPOP-3063
Executing multiple queries in parallel could lead to authentication failures
if `MaxInProcessPerConnection` is set to a value higher than `1` as the second
request could then be sent to the server while the server was still waiting for
the authentication challenge response from the driver for the first query.
This made it necessary to set `MaxInProcessPerConnection=1` as a workaround
for such scenarios which of course means that connection pooling is less
efficient.
Simply sending a validation request on each connection right after
establishing the connection and therefore before it can be used to submit
queries from the user should fix this issue. The downside of this is of course
that connection establishment takes slightly longer. I think this is an
acceptable trade-off even for scenarios where authentication is not used since
this also validates the connection irrespective of authentication and also
because this delay only occurs once right at the start of an application.
VOTE +1
> Concurrent queries will break authentication on .NET driver
> -----------------------------------------------------------
>
> Key: TINKERPOP-3063
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3063
> Project: TinkerPop
> Issue Type: Bug
> Components: dotnet
> Affects Versions: 3.6.6, 3.7.1
> Reporter: Florian Hockmann
> Assignee: Florian Hockmann
> Priority: Major
>
> Executing multiple queries in parallel can lead to authentication failures if
> {{MaxInProcessPerConnection}} is set to a value higher than {{1}} as the
> second request can then be send to the server while the server is still
> waiting for the authentication challenge response from the driver for the
> first query.
> A simple workaround is to set {{MaxInProcessPerConnection=1}} but this means
> of course that connection pooling will be less efficient.
> This issue also exists for other drivers:
> * Java: TINKERPOP-2132
> * JS: TINKERPOP-3061
> (I don't know about the Python and Go drivers.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
