Hi.
Dan did a nice demo, see a 'throttling' demo in the distribution, it
uses a Codahale library to do the advanced rate invocation checks,
right now it can delay the overflowing responses using the suspended
invocations mechanism, from 3.1.6 one would be able to abort such
requests with whatever HTTP error is preferred, 429/503, etc
(Dan, please review the minor changes I just did...)
Please experiment with the demo,
Sergey
On 01/02/16 11:12, Sergey Maslov wrote:
Hi!
I have web application that provides several soap service endpoints and
consumes several services as clients.
One of endpoints receives too many requests so it consumes much cpu
resources and the rest of application services freeze.
We also get "Executor queue is full, run the oneway invocation task in
caller thread" message, but increasing executor queue doesn't help as the
reason is heavy load.
Now we think of application redesign and moving to microservices, but it is
not easy deal. But we want to have some fast solution for right now.
For example, is it possible to limit threads or connections for
CXF endpoint calls? The desired behavior that if some external service
calls our endpoint and the connection size extends the limit, the caller
receives connection timeout or some other connection status. And our
application remains stable.
Thank you in advance.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
