[
https://issues.apache.org/jira/browse/GEODE-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723406#comment-16723406
]
ASF subversion and git services commented on GEODE-6177:
--------------------------------------------------------
Commit 14fee9aaa1e1fe82cc0adfce98df29521279e981 in geode's branch
refs/heads/develop from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=14fee9a ]
GEODE-6177: Spotless
> Gateway senders can shut down due to authentication failures
> ------------------------------------------------------------
>
> Key: GEODE-6177
> URL: https://issues.apache.org/jira/browse/GEODE-6177
> Project: Geode
> Issue Type: Bug
> Components: security, wan
> Reporter: Ryan McMahon
> Assignee: Ryan McMahon
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When a gateway sender connects to a gateway receiver and authentication is
> used, the receiver first determines if the provided credentials are valid.
> If they are valid, then event processing/dispatching is allowed.
> However, once the initial authentication is performed, it is possible that
> the gateway sender stops processing events if the connection with the
> receiver is destroyed and the credentials used are no longer valid
> (disallowed, password changed, etc).
> This is an edge case where the ack reader thread is the first to attempt to
> acquire the connection, rather than the dispatcher thread. The ack reader
> thread currently does not have the proper retry logic for authentication
> exceptions, while the dispatcher thread does. We should ensure that
> connection retries occur regardless of which thread gets the authentication
> exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
