Skip to main content

jax-ws (.2.2.5) handing of RejectedExecutionException thrown by Executor set via Endpoint.setExecutor

Please note these forums are being decommissioned and use the new and improved forums at
No replies
Joined: 2011-11-16

jaxws supports setting an Executor into the Endpoint for the purpose of "gain better control over the threads". However, WSHttpHandler does not provide any specific handling for that Executor rejecting the execute request, with the apparent result that no error is propagated back to the client and it is left hanging. The desire here is to cap or throttle the maximum number of concurrent requests the web service will handle, and to propagate that error back to the client immediately.

Is there another way to do this or a work around to achieve this behavior?