You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Florian Hockmann (Jira)" <ji...@apache.org> on 2024/03/13 14:12:00 UTC
[jira] [Created] (TINKERPOP-3063) Concurrent queries will break authentication on .NET driver
Florian Hockmann created TINKERPOP-3063:
-------------------------------------------
Summary: 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.7.1, 3.6.6
Reporter: Florian Hockmann
Assignee: Florian Hockmann
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)