Skip to content
This repository has been archived by the owner on May 28, 2018. It is now read-only.

Support ClientProperties.ASYNC_THREADPOOL_SIZE #2494

Closed
glassfishrobot opened this issue Nov 12, 2013 · 4 comments
Closed

Support ClientProperties.ASYNC_THREADPOOL_SIZE #2494

glassfishrobot opened this issue Nov 12, 2013 · 4 comments

Comments

@glassfishrobot
Copy link

So far, the ClientProperties.ASYNC_THREADPOOL_SIZE property 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.

Affected Versions

[2.4.1]

@glassfishrobot
Copy link
Author

Reported by raph.w

@glassfishrobot
Copy link
Author

raph.w said:
I suggested a fix in https://github.com/jersey/jersey/pull/39

@glassfishrobot
Copy link
Author

Marked as fixed on Tuesday, December 17th 2013, 8:05:45 am

@glassfishrobot
Copy link
Author

This issue was imported from java.net JIRA JERSEY-2222

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants