[
https://issues.apache.org/jira/browse/TINKERPOP-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835174#comment-17835174
]
Florian Hockmann commented on TINKERPOP-3063:
---------------------------------------------
Yes, sure. I think this is a duplicate of TINKERPOP-3061 so I'll close it as
such.
No need to also fix this for 3.6 in my opinion, especially not just for .NET
where most users just use the latest release any way.
> 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)
