Re: ClientBuilder#executorService

Pavel Bucek


good question, thanks.

Managed executor service references JSR 236 and I'd expect that when not present, the jndi lookup described in the spec would return null and jax-rs implementation will then fallback to "java se" case.

Thanks for pointing that out, I guess we'd need to rephrase the condition to something like "When JSR 236 is available, provided managed executor service has to be used as an executor service for asynchronous client calls."


On 18/05/2017 18:49, Guillermo González de Agüero wrote:

Perhaps this is a naive question, but how is the "managed" executor service handled on the Web Profile? Does "managed" mean that it must use a JSR 236 executor, or does it just refer to any "container managed" one?

The Web Profile does not include JSR 236, hence my question.


Guillermo González de Agüero

El jue., 18 de mayo de 2017 17:37, Pavel Bucek <pavel.bucek@...> escribió:
Dear experts,

please let me know if you find anything wrong with following statements:

on Java EE container:

     - JAX-RS client will use ManagedExecutorService for async/reactive
calls unless set explicitly by ClientBuilder#executorService

on Java SE:

     - JAX-RS client will use undefined, implementation specific
ExecutorService for async/reactive call, unless set explicitly by


Join to automatically receive all group messages.