[
https://issues.apache.org/jira/browse/TINKERPOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831274#comment-17831274
]
ASF GitHub Bot commented on TINKERPOP-3063:
-------------------------------------------
FlorianHockmann commented on PR #2522:
URL: https://github.com/apache/tinkerpop/pull/2522#issuecomment-2022386126
> Do you have any thoughts on the server side solution by @tien in
https://github.com/apache/tinkerpop/pull/2525? If the server fix fully
addresses the issue, then it should make the changes here as well as equivalent
GLV changes unnecessary.
I'm just back from vacation which is why I couldn't review the PR yet.
But I agree in general that a server fix is definitely better in general
than implementing workarounds in all GLV drivers. I'll try to review #2525
today.
If it fixes the issue, then we of course don't need this PR any more.
> 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)
