You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Owen Nichols (Jira)" <ji...@apache.org> on 2022/06/22 20:47:04 UTC
[jira] [Closed] (GEODE-9875) AuthenticationRequiredException: Failed to find the authenticated user.
[ https://issues.apache.org/jira/browse/GEODE-9875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen Nichols closed GEODE-9875.
-------------------------------
> AuthenticationRequiredException: Failed to find the authenticated user.
> -----------------------------------------------------------------------
>
> Key: GEODE-9875
> URL: https://issues.apache.org/jira/browse/GEODE-9875
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Reporter: Jinmei Liao
> Assignee: Jinmei Liao
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available, unreleased
> Fix For: 1.15.0
>
>
> Client connects to a server:
> One thread is doing puts using the connection with a valid uniqueId
> The ClientCacheUpdater thread failed to initialize, gets an IOException while trying to connect to the server:
> {quote}
> [warn 2021/12/06 17:41:16.345 PST edgegemfire1_host1_9691 <queueTimer-brloader1> tid=0x37] Cache Client Updater Thread on rs-RunItNow-HQ1613a0i3large-hydra-client-30(bridgegemfire1_host1_13308:13308)<ec><v9>:41001 port 23326 (rs-RunItNow-HQ1613a0i3large-hydra-client-30:23326): Caught following exception while attempting to create a server-to-client communication socket and will exit: java.net.SocketTimeoutException: Read timed out
> {quote}
> Then the ClientCacheUpdator resets the connections userId back to -1.
> The put thread uses this -1 as the uniqueId and then gets the exception back.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)