Skip to content
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

fixed: Ensure that the DnsNameResolver is closed when the AlgoliaClient is #511

Merged
merged 1 commit into from
Jan 8, 2019

Conversation

aseure
Copy link
Contributor

@aseure aseure commented Jan 7, 2019

Q A
Bug fix? yes
New feature? no
BC breaks? no
Related Issue Fix #500
Need Doc update no

Describe your change

Make sure that DnsNameResolver.close() is called when the AlgoliaClient.close() is called.

What problem is this fixing?

Problem is better described in #500 but essentially, prior to that fix, sockets were leaked and could lead to exhaustion when many AlgoliaClient got instantiated in the same JVM.

@Ant-hem @ElPicador If you guys could help me know how to run a single ScalaTest with specific JVM options, I'd be happy to know because I couldn't find an easy way of doing so to integrate the test suggested by @tanin47 in his issue. Thanks in advance for any help.

@aseure aseure changed the title fixed: Ensure that the DnsNameResolver is closed when the AlgoliaClie… fixed: Ensure that the DnsNameResolver is closed when the AlgoliaClient is Jan 7, 2019
@Ant-hem Ant-hem force-pushed the close-dns-resolver-properly branch from 2260010 to 6b937d8 Compare January 7, 2019 16:16
@Ant-hem Ant-hem merged commit 9c25f35 into master Jan 8, 2019
@Ant-hem Ant-hem deleted the close-dns-resolver-properly branch January 8, 2019 08:40
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.

Close dnsNameResolver in AlgoliaHttpClient.close()
2 participants