This solution is intended for the provider site not for the consumer
site. So what I mean is to limit the outgoing connections from
servicemix (for example to an external web service) over the provider
endpoint with the thread limit. It doesn't depend on the consumer
site.
Do you know what I mean or did I get something wrong?
You still have potentially the same problem as if you allow outgoing
connections to propagate uncontrollably you will start to saturate the
network layer leading to dropped packets, escalating retries and
eventual bottleneck backing up to the sending threads. Since this can
also disrupt other systems on the network it can turn into a
self-inflicted DOS Attack.
The system must play nicely with others in a production environment
where scarce resources need to be shared (often in order of priority).
--
Terry
