-
Notifications
You must be signed in to change notification settings - Fork 254
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
Calling HttpClient.shutdown() causes problem to later created clients #195
Comments
To prevent from closing the even loop, increment its refCount, like in the example below:
If you look into RxNetty source code, the default provider implementation is also |
Had a chat with @tbak .. the current code is wrong in shutting down the eventloop as it assumes that the following scenario is not valid: -- Create a bunch of clients The current global client holding the eventloop from shutdown is more of a side-effect than a design. So, I will remove the eventloop shutdown from the client for now. Since, the eventloops are always daemon threads, they will be alive only for the lifetime of the application. |
Here's the code that reproduces the problem:
The stack trace is:
The text was updated successfully, but these errors were encountered: