Skip to content

GEODE-4007: Authentication/Handshake errors should close the socket#1087

Merged
upthewaterspout merged 1 commit intoapache:developfrom
WireBaron:feature/GEODE-4007
Dec 6, 2017
Merged

GEODE-4007: Authentication/Handshake errors should close the socket#1087
upthewaterspout merged 1 commit intoapache:developfrom
WireBaron:feature/GEODE-4007

Conversation

@WireBaron
Copy link
Copy Markdown

@PivotalSarge @galen-pivotal @bschuchardt @upthewaterspout

This will cause the connection to be closed whenever a handshake or
authentication message fails.
The connection will also be broken if we ever receive an unexpected handshake or
authenticantication message.

Signed-off-by: Brian Rowe browe@pivotal.io

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

  • Has your PR been rebased against the latest commit within the target branch (typically develop)?

  • Is your initial contribution a single, squashed commit?

  • Does gradlew build run cleanly?

  • Have you written or updated unit tests to verify your changes?

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

Result<Resp, ErrorResp> process(SerializationService serializationService, Req request,
MessageExecutionContext messageExecutionContext) throws InvalidExecutionContextException;
MessageExecutionContext messageExecutionContext)
throws InvalidExecutionContextException, ConnectionStateException;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is ConnectionStateException still thrown? Or is the throws just inherited from ConnectionStateProcessor?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ConnectionStateException is newly thrown in this change, Galen made the observation that the code we're using to handle this inside the OpHandler is identical to the catch code we're using in the function calling this.

This will cause the connection to be closed whenever a handshake or
 authentication message fails.
The connection will also be broken if we ever receive an unexpected handshake or
 authenticantication message.

Signed-off-by: Galen O'Sullivan <gosullivan@pivotal.io>
@WireBaron
Copy link
Copy Markdown
Author

Also force pushed a new version with some commits that were missed.

@upthewaterspout upthewaterspout self-assigned this Dec 5, 2017
Copy link
Copy Markdown
Contributor

@upthewaterspout upthewaterspout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 I'll merge this.

@upthewaterspout upthewaterspout merged commit 5063aca into apache:develop Dec 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants