You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Blake Bender (JIRA)" <ji...@apache.org> on 2019/07/06 18:33:00 UTC
[jira] [Resolved] (GEODE-6835) AuthenticationException when using
subscription and AuthInitialize
[ https://issues.apache.org/jira/browse/GEODE-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Blake Bender resolved GEODE-6835.
---------------------------------
Resolution: Fixed
[https://github.com/apache/geode-native/pull/500] has the full description and fix. NC was sending a request to the server it no longer accepts, and when a security manager is in use this causes the server behavior described.
> AuthenticationException when using subscription and AuthInitialize
> ------------------------------------------------------------------
>
> Key: GEODE-6835
> URL: https://issues.apache.org/jira/browse/GEODE-6835
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Blake Bender
> Priority: Major
>
> When using subscription and AuthInitialize in conjunction while doing region puts in a loop, the Geode server eventually appears to think the connection is dead and throws an AuthenticationException. Correct behavior in this circumstance, according to the Geode team, is to attempt to re-authenticate and continue on. Again according to Geode, the Java-based client has this retry logic and is working properly, but it appears the native client is missing retry logic in at least one code path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)