Daemonize event loop threads. #922
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This instructs the `EventLoopGroupFactory` to daemonize newly created event loop group threads as per Netty's `DefaultThreadFactory`. This allows applications to shutdown when the last user thread ends, without explicitly calling `close` to the Neo4j driver instance, which is in line with other database drivers such as Postgres JDBC or MySQL JDBC. In addition, this might become relevant with Netty 5 at some point in the future, too. See: netty/netty#2832.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This instructs the
EventLoopGroupFactoryto daemonize newly createdevent loop group threads as per Netty's
DefaultThreadFactory. Thisallows applications to shutdown when the last user thread ends, without
explicitly calling
closeto the Neo4j driver instance, which is inline with other database drivers such as Postgres JDBC or MySQL JDBC.
In addition, this might become relevant with Netty 5 at some point in
the future, too. See: netty/netty#2832.