-
Notifications
You must be signed in to change notification settings - Fork 1.6k
AsyncHttpClientConfig throws an exception if we pass a managed executor service #402
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
Comments
Which version did you use? |
I tried using 1.7.19 and 1.7.20 and it did not work (I see that this call is commented on the master but I did not try it) |
Maybe @rlubke can help on this. For the record: AHC line: https://github.com/AsyncHttpClient/async-http-client/blob/async-http-client-1.7.19/src/main/java/com/ning/http/client/AsyncHttpClientConfig.java#L1099 |
That EE Concurrent Utilities spec states the following for ManagedExecutorServices:
The branch logic referenced by Stephane tries to prevent the user from passing an ExecutorService that has already been shutdown, however, I given the above, I think we should remove that safety check. If the user in a non EE environment passes an invalid ExecutorService, we can let an error occur then. |
👍 |
That sounds good.
|
I've pushed 1.7.21-SNAPSHOT to sonatype maven repo. Mind giving it a shot and verify resolution? |
The problem is resolved. Thanks |
Glassfish 4 implementation of JavaEE 7 managed executor service throws an exception if a life cycle method is called e.g isShutDown
This method is called in AsyncHttpClientConfig if an applicationThreadPool is passed to it.
The text was updated successfully, but these errors were encountered: