[
https://issues.apache.org/jira/browse/CXF-4312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-4312.
------------------------------
Resolution: Fixed
> JAX-WS clients set executor to a "thread per async request" version
> -------------------------------------------------------------------
>
> Key: CXF-4312
> URL: https://issues.apache.org/jira/browse/CXF-4312
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.3.10, 2.4.7, 2.5.3, 2.6
> Reporter: Daniel Kulp
> Assignee: Daniel Kulp
> Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11
>
>
> The JAX-WS ServiceImpl used on the client side sets the Executor for the
> client to OneShotAsyncExecutor which creates a thread for each async request.
> This doesn't allow transports such as the HTTPConduit to use the configured
> workqueues and there isn't any control over the number of threads created.
> The TCK does not require the executor. I also verified that the RI's
> service.getExecutor returns null if an executor is not set. Thus, setting
> this is not required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
