This repository has been archived by the owner on May 28, 2018. It is now read-only.
JERSEY-2222: Support ClientProperties.ASYNC_THREADPOOL_SIZE #39
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
…rty is ignored by the Jersey implementation. However, it should be considered by the ClientAsyncExecutorsFactory which can retreive a CommonConfig instance from its creating ClientRuntime as long as this instance is informed by its building ClientConfig. In dependency of the feature, a cached thread pool or a fixed thread pool can be used.
|
Jersey - JAX-RS Reference Implementation » jersey #151 FAILURE |
|
Has been resolved via internal commit. Still. thank you for your contribution submission. |
This was referenced Apr 19, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
So far, the
ClientProperties.ASYNC_THREADPOOL_SIZEproperty is ignored by the Jersey implementation. However, it should be considered by theClientAsyncExecutorsFactorywhich can retreive aCommonConfiginstance from its creatingClientRuntimeas long as this instance is informed by its buildingClientConfig.In dependency of the feature, a cached thread pool or a fixed thread pool can be used.
I already filed a Jira issue.