[
https://issues.apache.org/jira/browse/GEODE-9792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17437066#comment-17437066
]
Jinmei Liao commented on GEODE-9792:
------------------------------------
This problem exists in previous versions, but in previous versions, each
authentication request will get a new uniqueId, so the old uniqueId is never
used, the only harm is the "authenticate" method will be called multiple times
unnecessarily. But in 1.15, we are reusing the uniqueId from the same client
and logging out the previous user immediately (will be fixed soon), so we are
seeing some threads getting "FailedToFindAuthenticatedUser" failure (only in
the unreleased 1.15).
> Client in some cases would send in AuthenticationRequest multiple times even
> when they share the same connection
> ----------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-9792
> URL: https://issues.apache.org/jira/browse/GEODE-9792
> Project: Geode
> Issue Type: Bug
> Components: core
> Affects Versions: 1.15.0
> Reporter: Jinmei Liao
> Assignee: Jinmei Liao
> Priority: Major
> Labels: GeodeOperationAPI, needsTriage, pull-request-available
>
> It's observed that AuthenticationRequest will come in multiple times in the
> same connection by different threads.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
