Skip to content

Tls connections throw ServiceUnavaliable after restart of server #304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 17, 2017

Conversation

zhenlineo
Copy link
Contributor

Fixed the bug where tls connections are failed with ClientException, while plaintext connections are failed with ServiceUnav when server restart.
#302

…viceUnav when failed to establish connections
Copy link
Contributor

@lutovich lutovich left a comment

Choose a reason for hiding this comment

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

@zhenlineo looks good. Pointed out one possible simplification.

public class ServerKilledIT
{
@Rule
public TestNeo4j neo4j = new TestNeo4j();

@Parameters(name = "{0} connections")
public static Collection<Object[]> data() {
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we make this method return a collection of Config.EncryptionLevel? I think it'll make code simpler - no need for ignored testName constructor argument and flat list of Config.EncryptionLevel can be returned.

Changed to use encryption level to make the code easier to read
@lutovich lutovich merged commit fbdfd00 into neo4j:1.1 Jan 17, 2017
@lutovich lutovich deleted the 1.1-tls-connection-error branch January 17, 2017 09:57
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.

2 participants