[CXF-4312] JAX-WS clients set executor to a "thread per async request" version

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.10, 2.4.7, 2.5.3, 2.6
• Fix Version/s: 2.3.11, 2.4.8, 2.5.4, 2.6.1
• Component/s: JAX-WS Runtime
• Estimated Complexity: Unknown
• Assignee: Daniel Kulp
• Reporter: Daniel Kulp
• Created: 11/May/12 15:40
• Updated: 05/Jun/12 13:31
• Resolved: 11/May/12 17:51

Description

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.